Tuple encoding aware direct memory access engine for scratchpad enabled multicore processors

ABSTRACT

Techniques are described herein for efficient movement of data from a source memory to a destination memory. In an embodiment, in response to a particular memory location being pushed into a first register within a first register space, the first set of electronic circuits accesses a descriptor stored at the particular memory location. The descriptor indicates a width of a column of tabular data, a number of rows of tabular data, and one or more tabular data manipulation operations to perform on the column of tabular data. The descriptor also indicates a source memory location for accessing the tabular data and a destination memory location for storing data manipulation result from performing the one or more data manipulation operations on the tabular data. Based on the descriptor, the first set of electronic circuits determines control information indicating that the one or more data manipulation operations are to be performed on the tabular data and transmits the control information, using a hardware data channel, to a second set of electronic circuits to perform the one or more operations. Based on the control information, the second set of electronic circuits retrieve the tabular data from source memory location and apply the one or more data manipulation operations to generate the data manipulation result. The second set of electronic circuits cause the data manipulation result to be stored at the destination memory location.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is related to U.S. patent application Ser. No.15/074,248, entitled Run Length Encoding Aware Direct Memory AccessFiltering Engine for Scratchpad Enabled Multicore Processors, filed onthe equal day herewith by David Brown, et al., the entire contents ofwhich are incorporated herein by reference.

TECHNICAL FIELD

The technical field relates to data movement by hardware data movementsystem.

BACKGROUND

Database servers that execute on multi-core processors perform datamanipulation operations on large amounts of tabular data. Tabular datais data that is logically organized as rows and one or more columns,each column having a certain size, each row including each column.Logically, tabular data resides in a table-like structure, such as aspreadsheet or relational table. However, the actual physical storage ofthe tabular data may take a variety of forms. For example, in row-majorformat, tabular data may be stored as rows that are stored contiguouslywithin a memory address space, each row including each column and agiven column occupying the same number of bytes within a row. Incolumn-major format, each column may be separately stored from othercolumns as a column vector stored contiguously within a memory address,the particular entry for each row in a column vector being stored in thesame relative position or index of the respective column vector of eachother column.

To perform data manipulation operations on tabular data efficiently,tabular data is moved from main memory to a memory closer to a coreprocessor, where the operations can be performed more efficiently by thecore processor. Thus, the movement of tabular data between the memorycloser to a core processor and main memory is the type of operation thatis performed frequently by database servers.

However, approaches for moving tabular data to a memory closer to thecore processor add overhead that significantly offsets or eliminate anyadvantage gained by the movement of tabular data to the memory closer tothe core processor. Even direct memory access (DMA) engines capable ofoffloading the task of moving data cannot offer sufficient increase inprocessor efficiency for several reasons. Tabular data processed bydatabase operations is not organized or formatted in a way that isoptimal for a DMA engine to move.

Additionally, the memory closer to the core processor is typically smallin size. Therefore, a DMA engine will be able to move only a smallportion of data into the local memory before that memory is full andneeds to be emptied before it needs to be written to again. This resultsin the DMA engine repeating the process multiple times and issuing aninterrupt each time the DMA moves data to the memory closer to the coreprocessor, resulting in large number of interrupts. A large number ofinterrupts deteriorate core processor performance because every time thecore processor is interrupted, the core processor must determine thesource of the interrupt and how to handle the interrupt.

Furthermore, in multi-core processor architectures, where each core hasits own local memory, a DMA engine is required per core in order toaccess the local memory of the core. Implementing a DMA engine per coredramatically increases the cost, in terms of gate count, area and powerneeded, of such multi-core processor architectures

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 illustrates an example arrangement of a plurality of electroniccircuits of the data movement system.

FIG. 2 illustrates an example of descriptors to move data from a sourcememory location to a destination memory location.

FIG. 3 illustrates an example of descriptors for moving data stored intabular format.

FIG. 4 illustrates an example of descriptors for performing datamanipulation operations on one or more

FIG. 5 illustrates an example arrangement of data manipulation operationblocks

FIG. 6 illustrates an example process for moving data using hardwarecircuitry without execution of software.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to avoid unnecessarily obscuring thepresent invention.

General Overview

The techniques described herein provide for accessing tabular data at asource memory location and copying and storing the tabular data at adestination memory location without executing software programs.Additionally, the techniques also provide for performing one or moredata manipulation operations, again without executing software programs,on the tabular data while the data is in flight to the destinationmemory location. In other words, data manipulation operations willtypically be performed within the same clock cycles that are used intransmitting the data to the destination memory location and prior tostoring the tabular data at the destination memory location.Consequently, the tabular data stored in the destination memory locationis the tabular data resulting from the data manipulation operations.Therefore, the core processor can avoid spending additional clock cyclesin manipulating the tabular data.

In an embodiment, in response to a particular memory location beingpushed or stored into a first register within a first register spacethat is accessible by a first set of electronic circuits, the first setof electronic circuits access a descriptor stored at the particularmemory location. The descriptor may indicate a source memory location ofwhere the said tabular data is stored, and the descriptor may alsoindicate a destination memory location to store the result of a datamanipulation operation. The destination memory location may be within amemory that is local to the core data processor that programmed thedescriptor. With the memory being local to the core data processor, thedistance between the core data processor and the memory is short,therefore the latency in accessing the tabular data from the destinationmemory location is reduced. Performance of the core processor inaccessing the tabular data is improved.

The descriptor may also indicate a width of a column of tabular data,wherein the tabular data comprises columns and rows, a number of rows oftabular data. By describing the tabular data to be moved in terms ofnumber of rows and width of the column of tabular data, the descriptorspecifies to the data movement system how a database column of adatabase table is formatted and stored at the source memory location.Different columns of the database table may be specified by differentdescriptors, thus the data movement system is fully aware of howdatabase tables are formatted and stored at the source memory location.Therefore, the data movement system is always optimized to accesstabular data from a source memory location and store it in a destinationmemory location, depending on how the tabular data is formatted andorganized at the source memory location.

The descriptor may also indicate one or more tabular data manipulationoperations to perform on the column of data. An example of a tabulardata manipulation operation may be a type of filtering operation,described herein as a gather operation. The descriptor may indicate thata gather operation should be performed on the tabular data. Thedescriptor may also specify a memory location of a bit vector within thelocal memory. The data movement system, described herein, uses the bitvector specified by the descriptor to filter out rows of the column oftabular data that do not satisfy the filtering criteria. The datamovement system filters out rows of the column of tabular data while thedata is in flight to the destination memory location or prior to thetabular data being stored in the destination memory location, andcompacts the resulting rows, the rows that were not filtered out, whilestoring the resulting rows in the destination memory location such thatthe resulting rows are stored in consecutive memory locations withindestination memory even if the resulting rows were not stored inconsecutive memory locations at the source memory location.

Therefore, the number of rows of the column of tabular data stored inthe destination memory location after a gather operation is performedwill likely be fewer than the number of rows specified by thedescriptor. Thus, in addition to performance gain mentioned above, amore efficient usage of the limited storage space within a memory localto a core in multi-core processor is achieved.

Based on the descriptor, the first set of electronic circuits determinecontrol information that indicate one or more data manipulationoperations to perform on the tabular data. Using a hardware datachannel, the first set of electronic circuits transmit the controlinformation to a second set of electronic circuits to perform the one ormore operations. The second set of electronic circuits, according to thecontrol information, retrieve the tabular data from a source memorylocation, and apply the one or more data manipulation operations to thetabular data to generate the data manipulation result and cause the datamanipulation result to be stored at the destination memory location.

Once the tabular data is stored at the destination memory location, thetechniques described herein allow the data movement system to notify thecore processor that data is available in the destination memory by usingevent identifiers that are associated with a particular descriptor. Thecore processor is capable of handling these event identifiers withoutneeding interrupt handlers. Thus, significantly reducing overhead costsof interrupt handlers.

The techniques described herein further allow the data movement systemto begin processing the next descriptor. The data movement system maybegin processing the next descriptor while the core processor processesthe tabular data stored at the destination memory location. In otherwords, processing of the next descriptor and accessing and processing oftabular data stored may occur simultaneously. Therefore, the coreprocessor may access and process data from the destination memory whilethe data movement system is moving tabular data for the next descriptorto a different destination memory location specified in that descriptor.Thereby significantly improving the speed of processing data.

In other embodiments, the disclosure encompasses a data movement systemand a computer apparatus to carry out the foregoing steps.

Overview of the Data Movement System

Core Processor and DMEM

FIG. 1 illustrates an example arrangement of a data movement system.FIG. 1 comprises a plurality of core processors 103 a, 103 g, 104 a, 104g. Each of the core processors 103 a, 103 g, 104 a, 104 g are connectedto a local high-speed scratchpad memory, such as a static random-accessmemory (SRAM), referred to herein as DMEM (Direct Memory). In FIG. 1,core processors 103 a, 103 g, 104 a, 104 g are connected to DMEM units102 a, 102 g, 105 a, 105 g, respectively. Of all the core processors,only the processor that is connected to a particular DMEM may directlyaccess that particular DMEM. Thus, DMEM 102 a may be accessed by coreprocessor 103 a, but cannot be accessed by core processor 103 g, 104 a,104 g. DMEM 102 g may be accessed by core processor 103 g, but not bycore processors 103 a, 104 a, 104 g. Likewise, DMEM 105 a may beaccessed by core processor 104 a, but not by core processors 103 a, 103g, 104 g and DMEM 105 g may be accessed by core processor 104 g, butcannot be accessed by core processors 103 a, 103 g, 104 a.

Direct Memory Access Complex (DMAC)

The data movement system described herein comprises three majorfunctional blocks, Direct Memory Access Complex (DMAC), Direct MemoryAccess X-Bar (DMAX) and Direct Memory Access DMEM (DMAD). The datamovement system described herein comprises only one DMAC block andseveral DMAX and DMAD blocks. The DMAC comprises several complex dataretrieval, load and manipulation engines. The DMAX blocks mainlycomprise data routing engines and the DMAD blocks mainly comprise datadecoding engines and descriptor channel blocks.

The data movement system described herein comprises one DMAD block percore, therefore the number of the DMAD blocks depend upon the number ofcores utilized in the data movement system. For example, a data movementsystem in a 32 core processor system, the number of DMAD blocks is 32.In an embodiment, several DMAD blocks may be configured to route dataand instructions to one DMAX block. Continuing with the example of the32 core processor, 8 DMAD blocks may be configured to route data andinstructions to one DMAX block, thereby resulting in 4 DMAX blocks toserve 32 DMAD blocks of 32 cores.

The data movement system described herein comprises only a single DMAC.The single DMAC processes data and instructions, routed via DMAX, fromall DMAD blocks of the data movement system. The DMAC comprises enginesthat perform complex functions and due to their complexity, require thehighest gate count, area and power relative to the engines within DMAXand DMAD blocks. Therefore, the DMAC impacts the total cost of the datamovement system more than DMAX and DMAD blocks. However, by sharing theDMAC resources across the DMAX and DMAD blocks, the cost of a DMAC tothe data movement system is amortized. Thus, the total cost of the datamovement system, in terms of gate count, area and power, issubstantially lower than alternative approaches described above.

In an embodiment, the data movement system described herein isimplemented on a single chip. Thus, for each core processor, the DMEMconnected to each of the core processors, the DMAD block for each of thecore processors, DMAX blocks and the DMAC block are all designed,implemented and configured on a single chip. A bus interconnects all thefunctional blocks of the data movement system in the chip.

FIG. 1 depicts Direct Memory Access Complex (DMAC) 140 and several majorengines of DMAC 140. The details and workings of DMAC 140 and itsengines are described further below.

Direct Memory Access DMEM (DMAD)

Each of the core processors, 103 a, 103 g, 104 a, 104 g, is connected toDMAD 106 a, 106 g, 115 a, 115 g, respectively. Each DMAD comprises agroup of electronic circuits that have been designed to receiveinstructions from the core processor connected to the particular DMAD.For example, DMAD 106 a is designed to receive instructions from coreprocessor 103 a only.

A core processor sends instructions to a DMAD by programming a set ofcommands, herein referred to as a descriptor. A descriptor describesmovement of data from one location to another location through aplurality of fields. Some of the fields in the descriptor may include adescriptor type, a source address location that indicates the sourcelocation for the tabular data to be moved from, a destination addresslocation that indicates the destination location for the tabular datafrom the source location to be copied to, the size of the column oftabular data to be operated on, the number of rows of the column oftabular data that need to be copied, one or more data manipulationoperations and wait-for event identifiers and other control flags.

Once the core processor programs the descriptor, the core processorstores the descriptor at a location in the DMEM. For example, coreprocessor 103 a upon programming the descriptor, stores it in DMEM unit102 a. Core processor 103 a then sends the descriptor to DMAD 106 a bytransmitting the memory location of the descriptor within the DMEM unit102 a onto one of the two hardware data channels of DMAD 106 a. A coreprocessor transmits the memory location of a descriptor onto a datachannel by storing the memory location into a register. In anembodiment, the register maybe designed to be a first-in-first-out orFIFO register such that the first memory location that is pushed orstored into the register will be the first memory location that is addedinto a hardware managed list of one of the two hardware data channels.

DMEM Interface Block

Each DMAD comprises a DMEM interface block that is configured to storeany data destined for the DMEM unit coupled with its DMAD, and generatea write request for the DMEM unit coupled with its DMAD to store thedata transmitted to its DMAD in the DMEM unit coupled with its DMAD. Forexample, DMAD 106 a comprises DMEM interface block 107 a. DMEM interfaceblock 107 a is a group of electronic circuits that have been designed tostore data transmitted to DMAD 106 a and destined for DMEM unit 102 a inone of the registers accessible by DMEM interface block 107 a.Additionally, the group of electronic circuits of DMEM interface block107 a have also been designed to generate a write request, for DMEM unit102 a, to store the data destined for DMEM unit 102 a. DMAD 106 g, 115a, and 115 g similarly comprise DMEM interface blocks 107 g, 109 a, 109g respectively.

The DMEM interface block is also configured to read or retrieve datafrom the DMEM unit coupled with its DMAD. The DMEM interface block maygenerate a read request, using a DMEM unit location, to read or retrievedata from the DMEM unit location. The DMEM interface block may receive aread request to read or retrieve data from a particular DMEM unitlocation and in response the DMEM interface block may read or retrievedata from the particular DMEM unit location. The DMEM interface blockmay transmit the read or retrieved data to the hardware component withinits DMAD that requested that data. The DMEM interface block may receivea write request to write or store data at a particular DMEM unitlocation and in response the DMEM interface block may write or storedata at the particular DMEM location in the DMEM unit coupled with theDMAD of the DMEM interface block. Each of DMEM interface blocks 107 a,107 g, 109 a, 109 g, depicted in FIG. 1, are designed to perform theabove operations with DMEM units 102 a, 102 g, 105 a, and 105 g,respectively.

Descriptor Channel Block of DMAD

Each DMAD comprises a Descriptor Channel Block, which is a subset ofelectronic circuits of the DMAD that are designed to determine thehardware data channel to which the descriptor will be added. In anembodiment, each DMAD may be designed to maintain two hardware datachannels, and may have two Descriptor Channel Blocks, one for each ofthe hardware data channels. For example, DMAD 106 a is designed tomaintain two hardware data channels. Descriptor Channel Blocks 108 a and108 b are the two descriptor channel blocks of DMAD 106 a. Similarly,DMAD 106 g comprises Descriptor Channel Blocks 108 g, 108 h, DMAD 115 acomprises Descriptor Channel Blocks 111 a, 111 b and DMAD 115 gcomprises Descriptor Channel Blocks 111 g, 111 h.

Each Descriptor Channel Block maintains two hardware managed lists, anactive list and a free list, per hardware data channel. In anembodiment, the hardware managed active list and free list are linkedlists. Once the core processor stores the DMEM location of thedescriptor into the FIFO register, the Descriptor Channel Block of theDMAD connected to the core processor transmits the DMEM location of thedescriptor from the FIFO register to one of the hardware data channels.In an embodiment, once the DMEM location of a descriptor is stored intoa FIFO register, the Descriptor Channel Block determines the number ofdescriptors that are assigned to be processed on that particularhardware data channel and if the number of descriptors that are assignedto be processed on that particular hardware data channel is greater thanzero, then the Descriptor Channel Block adds the new descriptoridentified by the newly pushed or stored DMEM location in the FIFOregister to the active list of that particular hardware data channel.The Descriptor Channel Block adds the new descriptor to the active listby transmitting instructions to the DMAD to write the DMEM location ofthe new descriptor to the Link Address field of the last descriptor thatwas added to that particular hardware data channel.

The Descriptor Channel Block begins processing a descriptor by storingthe DMEM location of the descriptor into a register that has beendesignated as the register from which the Descriptor Channel Block isdesigned to read from and start processing the next availabledescriptor, referred herein as the Next Descriptor to Read register. Ifthe active list is empty, then the Descriptor Channel Block stores theDMEM location from the FIFO register into the Next Descriptor to Readregister. If the active list is not empty, then the Descriptor ChannelBlock adds the descriptor, stored at the DMEM location from the FIFOregister, to the end of the active list by updating the Link Addressfield value of the descriptor previously at the end of the active listto contain the DMEM location value from the FIFO register.

In an embodiment, a register, described herein as the Last DescriptorList register, accessible by the Descriptor Channel Block comprises theDMEM location of the descriptor that is currently at the end of theactive list. The Descriptor Channel Block adds a new descriptor to theactive list by storing or writing the DMEM location from the FIFOregister as the value of the Link Address field of the descriptorcurrently at the end of the list and storing the DMEM location valuefrom the FIFO register in the Last Descriptor List register. TheDescriptor Channel Block then traverses through the active list usingthe Link Address field of the descriptor that is currently beingprocessed.

Once the DMEM location of a Descriptor is stored in the Next Descriptorto Read register, the Descriptor Channel Block, using the DMEM locationstored in the register, retrieves the data of the descriptor availableat that DMEM location from the DMEM. The Descriptor Channel Blocktransmits a request to read data from DMEM to the DMEM Interface Blockof the DMAD. The request to read data includes the DMEM location of thedescriptor. In an embodiment, the request to read data also specifies anumber of bytes to read. In an embodiment the number of bytes to readequals the number of bytes that make up the entire descriptor or thetotal size of the descriptor. In an embodiment, the total size of adescriptor is 16 bytes. The DMEM Interface Block retrieves data fromDMEM using the specified DMEM location and forwards the data to theDescriptor Channel Block. The Descriptor Channel Block decodes thedescriptor data including, but not limited to, determining the type ofthe descriptor. The Descriptor Channel Block determines the type of thedescriptor and processes the descriptor based at least on the type ofthe descriptor.

Descriptor Types

According to an embodiment, there are at least three types ofdescriptors, which are data descriptors, control descriptors, auxiliarydescriptors. The type of the descriptor is indicated by a descriptortype field within the descriptor data. There are multiple variationswithin each type of descriptor. Data descriptors specify how DataMovement System moves data from one memory location to another memorylocation, and the data is transformed during movement.

Control descriptors provide information for looping through one or moredescriptors more than once. Additional control descriptors include (1)descriptors that may be used to program certain configurations withinthe data movement system, referred to herein as program descriptors, (2)descriptors that may be used to control event registers in the datamovement, referred to herein as event descriptors, and (3) descriptorsthat may assist with partitioning of tabular data, referred to herein ashash and range engine descriptors.

Auxiliary descriptors provide information that assist in the processingof another descriptor. For example, the auxiliary descriptor may be usedto provide additional control information if the size of the requiredcontrol information exceeds more than the maximum size allowed for thecontrol information.

Data descriptors, auxiliary descriptors and control descriptors thataffect registers or control state in the Direct Memory Access Complex(DMAC) 140 are forwarded to DMAC. Control descriptors that affect theregisters in a DMAD, that indicate loop mechanisms of one or moredescriptors, or other control descriptors that do not need to be sent toDMAC, or that affect registers designed to store data corresponding towait for events are further processed by the Descriptor Channel Block.

Direct Memory Access X-Bar (Cross-Bar)

Descriptors are forwarded to DMAC by forwarding the data of thedescriptors to Direct Memory Access Cross(X)-Bar (DMAX) 110 a, 110 d.DMAX comprises electronic circuits that are configured to control androute data flow from a DMAD to a DMAC and from the DMAC to the DMAD. Inan embodiment, the electronic circuits of a DMAX may be grouped into 3groups. One group of electronic circuits may be designed to transmit allcontrol information of descriptors from the DMAD to the DMAC, whileanother group of electronic circuits may be designed to transmit, fromthe DMAD to the DMAC all data corresponding to a response of a readrequest from the DMAC to the DMAD to read data from the DMEM. The thirdgroup of electronic circuits may be designed to transmit a read requestfrom DMAC to DMAD to read data from the DMEM. Additionally, the thirdgroup of electronic circuits may be designed to transmit all descriptorsreturn paths from the DMAC to the DMAD, wherein each descriptor returnpath comprises identifiers associated with a descriptor that indicatethe DMAD to which the descriptor belongs to, the descriptor channelblock within that DMAD that processed the descriptor and an identifierof that descriptor.

For example, DMAX 110 a comprises an arbitration unit, such as thearbitration unit 112 a and a FIFO register 112 b for transmitting datafrom DMAD 106 a to DMAC 140. In an embodiment, data includes controlinformation of a descriptor which may be used by the arbitration unit112 a in selecting one of the input data paths and transmitting dataincluding the control information into the FIFO register 112 b.Similarly, DMAX 110 a comprises FIFO register 114 b and routing unit 114a to transmit data from the DMAC to the DMAD. In an embodiment, datatransmitted from the DMAC may comprise control information such thatrouting unit 114 a selects the data path for the target DMAD to transmitthe data. DMAX 110 a also comprises another arbitration unit 113 a and aFIFO register 113 b for transmitting data to be copied from DMEM to anexternal storage memory.

DMAX 110 d comprises arbitration units 112 g and 113 g and routing unit114 g that provide the same functionality and perform the same functionsas arbitration units 112 a and 113 a and routing unit 114 a,respectively. DMAX 110 d also comprises FIFO registers 112 h, 113 h and114 h that provide the same functionality and perform the same functionsas 112 b, 113 b, 114 b respectively.

Direct Memory Access Complex (DMAC)—Write Descriptor Parser

DMAC 140 comprises a write descriptor arbitration unit 120 a, and theoutput of the write descriptor arbitration unit 120 a is stored in thewrite descriptor parser logic block 120 b. Write descriptor parser logicblock 120 b comprises one or more registers. Electronic circuits ofwrite descriptor parser logic block 120 b are designed to accumulatedescriptor data and control information transmitted from a DMAX. In anembodiment, descriptor data from the DMAX may be transmitted infragments, and electronic circuits of write descriptor parser logicblock 120 b may accumulate the various descriptor fields and reassemblethe descriptor fields to form the complete descriptor data. Writedescriptor parser logic block 120 b determines the descriptor type ofthe descriptor and performs operations based on the descriptor type andthe control information provided by the originating DMAD.

In response to determining that the descriptor is a data descriptor andin particular a write descriptor, write descriptor parser logic block120 b may modify the source address specified in the descriptor datausing a source counter value provided by the originating DMAD.Additionally, write descriptor parser logic block 120 b may also modifythe destination address using a destination counter value provided bythe originating DMAD. Write descriptor parser logic block 120 b alsotransmits a data movement operation and the descriptor data to anappropriate data movement engine such as a DMEM load engine.

If the descriptor type is an auxiliary type descriptor, then writedescriptor parser logic block 120 b may update a local auxiliary dataholding register and return the descriptor back to the originating DMAD.If the descriptor type is a program or control type descriptor, thenwrite descriptor parser logic block 120 b may store DMAC configurationdata specified within the descriptor in the DMAC configuration registerspecified in the descriptor, and return the descriptor back to theoriginating DMAD.

Direct Memory Access Complex (DMAC)—Read Descriptor Parser

DMAC 140 also comprises a read descriptor arbitration unit 121 a, andthe output of the read descriptor arbitration unit 121 a is readdescriptor parser logic block 121 b. Read descriptor parser logic block121 b comprises one or more registers. Electronic circuits of readdescriptor parser logic block 121 b are designed to accumulatedescriptor data and control information transmitted from a DMAX. In anembodiment, descriptor data from a DMAX may be transmitted in fragments,and electronic circuits of read descriptor parser logic block 121 b mayaccumulate the various descriptor fields and reassemble the descriptorfields to form the complete descriptor data. Read descriptor parserlogic block 121 b determines the descriptor type of the descriptor andperforms operations based on the descriptor type and the controlinformation provided by the origination DMAD.

In response to determining that the descriptor is a data descriptor andin particular a read descriptor, read descriptor parser logic block 121b may modify the source address specified in the descriptor data using asource counter value provided by the originating DMAD. Additionally,read descriptor parser logic block 121 b may also modify the destinationaddress using a destination counter value provided by the originatingDMAD. Read descriptor parser logic block 121 b also transmits a datamovement operation and the descriptor data to an appropriate datamovement engine such as a DDR load engine.

Similar to write descriptor parser logic block 120 b, if the descriptortype is an auxiliary type descriptor, then read descriptor parser logicblock 121 b may update a local auxiliary data holding register andreturn the descriptor back to the originating DMAD. If the descriptortype is a program or control type descriptor, then read descriptorparser logic block 121 b may store DMAC configuration data specifiedwithin the descriptor in the DMAC configuration register specified inthe descriptor, and return the descriptor back to the originating DMAD.

Direct Memory Access Complex (DMAC)—Data Movement Engines

DMAC 140 comprises data movement engines 130 a, 130 b, 130 c, 130 d.Each of the data movement engines 130 a, 130 b, 130 c, 130 d, compriseone or more DMEM load engines and one or more DDR load engines. Each ofthe data movement engines 130 a, 130 b, 130 c, 130 d also comprise oneor more DMEM store engine and one or more DDR store engines. Each datamovement engine receives operations from write descriptor parser logicblock 120 b, and read descriptor parser logic block 121 b. Data movementengines 130 a, 130 b, 130 c, 130 d execute these operations by copyingdata from the specified source memory and storing data in the specifieddestination memory. Each data movement engine also uses controlinformation provided by the descriptor parser logic block to theirexecute operations.

Data movement engines 130 a, 130 b, 130 c, 130 d generate read requeststo the specified source memory. Data movement engines 130 a, 130 b, 130c, 130 d accumulate data transmitted to the data movement engine inresponse to the read request, and then generate write requests to thespecified destination memory. In an embodiment, a buffering process isimplemented such that data transmitted to data movement engines may bestored in a register block accessible by the data movement engines. Datamovement engines begin processing data transmitted in response to theread request without waiting for the requested data to be available.

Electronic circuits of system bus interface master block 123 aredesigned to the receive read and write requests from the data movementengines 130 a, 130 b, 130 c, 130 d and translate them into system businterface read requests and system bus interface write requests formemory units external to the data movement system, such as main memoryor another memory unit. Electronic circuits of system bus interfacemaster block 123 transmits data it receives in response to system businterface read requests to the data movement engine that transmitted theread request. In an embodiment the system bus interface is AXI (AdvancedExtensible Interface) and system bus interface master block 123 is anAXI master block.

Descriptor return block 125 is designed to return descriptors processedby write descriptor parser logic block 120 b, read descriptor parserlogic block 121 b, and data movement engines 130 a, 130 b, 130 c, 130 d,to their originating DMAD.

DMS memory 150 comprises memory that various components of DMAC 140 mayread from or write to. In general, DMS memory 150 is used to store dataused by or generated by operations performed by the DMAC 140.

Supplemental Operation Engines 126 is representative of blocks of logic,each block performing a specific kind of operation on columns stored inDMS memory 150. For example, Supplemental Operation Engines 126 mayinclude a partitioning engine that partitions tuples stored in one ormore columns stored in DMS memory 150 among core processors in the datamovement system. Such partitioning may include generating for each tuplean identifier identifying a co-processor to which the tuple is assignedby partitioning.

In addition, Supplemental Operation Engines 126 may include a hashengine. The hash engine generates hash values for one or more columnsstored in DMS memory 150. Another example of an engine that may beincluded is a copy engine. The copy engine copies data between memorylocations within DMS memory 150.

Moving Data and Performing Data Manipulation Operations UsingDescriptors

FIG. 2 illustrates an example method of moving data from a source memorylocation to a destination memory location using descriptors. FIG. 2comprises three descriptors, 201 a, 202 a, 203 a. Elements 201 b, 202 band 203 b each correspond to operations performed for descriptors 201 a,202 a, 203 a, respectively. The purposes of these elements is depict theorder of operations performed for descriptors 201 a, 202 a, 203 a.

FIG. 2 depicts a movement of ten thousand rows of data from a sourcememory location to a target memory location. In this example the sourcememory location is a double data rate synchronous dynamic random-accessmemory (DDR) and the target memory location is the DMEM connected to thecore processor that programmed the descriptor, 102 a and 103 arespectively. In the example depicted in FIG. 2, descriptors 201 a, 202a, 203 a are programmed by core processor 103 a.

Decoding Descriptor Data

Descriptors 201 a and 202 a are data descriptors. The descriptor typefield of the descriptors indicates that descriptors 201 a and 202 a aredata descriptors. In an embodiment, binary numbers may be used to depicteach descriptor type and direction in which the data is to be moved. Forexample, binary number 0000 may be encoded in the electronic circuits ofthe descriptor channel block of the DMAD that is processing thedescriptors to represent data movement from DDR memory to DMEM memory orDMEM. Similarly, data movement from DMEM to DDR memory may berepresented by binary number 0001. For descriptors 201 a and 202 a, datais to be moved from DDR memory to DMS memory or DMEM memory. Therefore,descriptor type field of descriptor 201 a, 202 a indicate theappropriate field value. The value of the “Desc Type” field shown inFIGS. 201a and 202a is only for providing a clear illustrative example.

The core processor determines the source location of the source dataalong with the destination location of where the data is to betransmitted. The core processor also determines the number of rows thatare to be processed at the source data location by a descriptor. In anembodiment, the core processor may be configured with a maximum numberof rows that a descriptor is allowed to process. Such thresholdlimitation may be dynamically determined based on the size of DMEM orthe available storage space in DMEM.

In FIG. 2, since the total number of rows of data that are to beprocessed is at least ten thousand rows, the core processor alsoprograms a control descriptor that allows a DMAD to utilize the samedescriptor numerous times. In other words the control descriptor allowselectronic circuits of the DMAD to implement a loop mechanism until somecondition within the control descriptor is not satisfied. Controldescriptors that allow the DMAD to implement such a loop mechanism willbe referred to herein as loop descriptors.

In an embodiment, a core processor may also be configured to utilizemultiple buffers in the DMEM to store data from the source datalocation. Utilization of multiple buffers allows for the core processorto access the data stored in the DMEM faster and consequently processthat data faster than using a single buffer because it allows the coreprocessor to access data stored in one buffer while the data movementsystem is moving or storing data in the other buffers. The flexibilityof specifying different destination memory locations in differentdescriptors allows for the utilization of multiple buffers.

As described herein, a buffer is said to be associated with a descriptorif the destination memory location specified in the descriptor is thestarting memory location of the buffer. Each descriptor may representonly a fraction of the total number of rows of a column of tabular datathat is being moved into a DMEM unit. Thus the buffer associated with aparticular descriptor stores the fraction of the total number of rows ofthe column of tabular data and the core processor may begin processingthe rows stored in the buffer without waiting for remaining number ofrows of the column of tabular data being moved or stored into theirrespective buffers.

Additionally, the overhead costs from interrupt routines and interrupthandlers in switching control between the hardware components of thedata movement system and the software executing on the core processormay be reduced by utilizing wait-for-events. The core processor may beconfigured to assign a particular event to a particular buffer in theDMEM and the values of the particular event will determine whether thehardware components of the data movement system will have access to theparticular buffer or whether the software executing on the coreprocessor will have access to the particular buffer.

In FIG. 2, descriptor 201 a is assigned Event0. Based on theconfiguration, core processor 103 a may either set Event0 to a value of1 or 0 in order to allow the hardware components of the DMAD to processthe descriptor. For example, if the electronic circuits of the DMAD 106a have been designed to begin the processing of the descriptor only ifEvent0 is set to be zero, then core processor 103 a will set the Event0value to 0 after core processor 103 a programs the descriptor. Coreprocessor 103 a does not access that particular buffer until the valueof Event0 is set to one. DMAD 106 a will set the value of Event0 to 1when the Buffer0 201 b is full.

In FIG. 2, within the DMEM unit 102 a, the data is being stored in twobuffers, one at address 0x0000 and another at address 0x2000. Asdescribed above, using at least two buffers enables faster processing ofdata. Once the DMAD 106 a and other hardware components of data movementsystem begin processing descriptor 201 a, data associated with thatdescriptor will be stored in Buffer0 at address 0x0000 of DMEM unit 102a. Once Buffer0 has been filled with data, DMAD 106 a will set theEvent0 value to 1, which will indicate to core processor 103 a thatBuffer0 is ready to be accessed and data in Buffer0 is ready to beprocessed. After the processing of descriptor 201 a is completed thefirst time, DMAD 106 a and other hardware components of the datamovement system will begin processing descriptor 202 a. While thehardware components of the data movement system begin processingdescriptor 202 a, core processor 103 a will be processing data fromBuffer0. Therefore, using two data buffers allows for processing datarecords on a subset of data records without waiting for the entire setof data records to be retrieved first. Thus, reducing processing timeand increasing processing speed.

In FIG. 2, descriptor 201 a will be the first descriptor to be pushed onto one of the two hardware data channels of DMAD 106 a and it will bethe first descriptor among descriptors 201 a, 202 a, 203 a to beprocessed. Descriptor 202 a will be processed after descriptor 201 a hasbegun processing and then descriptor 203 a will be the last descriptoramong the three descriptors to be processed, and descriptor 203 a willbe processed after descriptor 202 a has begun processing. The coreprocessor stores a descriptor in DMEM after programming the descriptorand in FIG. 2 core processor 103 a stores descriptor 201 a at address0x5000, descriptor 202 a at address 0x5010 and descriptor 203 a ataddress 0x5020 of DMEM or DMEM unit 102 a.

In FIG. 2, the “Src Addr” of descriptors 201 a and 202 a indicates thestarting location of the column of data within the source memory wherethe tabular data is stored. “Dest Addr” of descriptors 201 a and 202 aindicates the location in DMEM where the data from the source memorywill be stored. “Column Width” indicates the size of the data in thecolumn of data in bytes and “Rows” indicates the number of rows thatwill be processed each time the data movement system is processing thedescriptor 201 a or 202 a. Adescriptor may comprise a “Src Auto IncAllow” field, wherein the “Src Auto Inc Allow” field indicates to adescriptor parser logic block within the DMAC to modify the sourceaddress based on values of one or more other fields within thedescriptor. In an embodiment, the one or more other fields within thedescriptor include, the “Counter Inc” field, the “Column Width” fieldand the “Rows” field of the descriptor. The descriptor parser logicblock may modify the source address specified in the descriptor usingthe source address specified in the descriptor as a starting point or abase source address and adding an offset value to the base sourceaddress, wherein the offset value is determined by the descriptor parserlogic block based on the values of the source counter, the width of thecolumn of tabular data that is being moved or copied from the sourceaddress specified in the descriptor and the number of rows of the columnof tabular data that is being moved or copied from the source addressspecified in the descriptor.

As described above, the “Column Width” field of the descriptor specifiesthe width of the column of the tabular data and the “Rows” field of thedescriptor specifies the number of rows of the column of tabular data.The value of the source counter may be read or retrieved from a registercomprising the source counter. In some embodiments, the “Counter Inc”field of a descriptor specifies the register that comprises the sourcecounter value. In some embodiments, the “Counter Inc” field indicatesthat the counter value that should be considered or used is the sourcecounter value and the descriptor channel block is configured to retrievethe value stored in a particular register that comprises the sourcecounter value. In some embodiments, the descriptor channel block isdesigned to retrieve a source counter value from a particular registerthat has been designated to store source counter value.

The value of the“Src Addr Inc” field determines whether or not a counterspecified by the “Counter Inc” field should be incremented. In anembodiment, if the “Src Addr Inc” field is set then the counterspecified by the “Counter Inc” field is incremented by a descriptorchannel block processing the descriptor, and if the “Src Addr Inc” fieldis not set then the counter specified by the “Counter Inc” field is notincremented. In an embodiment, the descriptor channel block that isprocessing the descriptor increments the value of the counter specifiedby the “Counter Inc” field of a source counter associated with adescriptor channel block by the descriptor channel block.

In FIG. 2, the “Counter Inc” field of descriptor 201 a specifies thatthe counter is the source counter of the descriptor channel blockprocessing descriptor 201 a, which in FIG. 2, as described above, isdescriptor channel block 108 a. The “Src Addr Inc” field of descriptor201 a triggers the incrementing of the counter value specified by the“Counter Inc” field by the descriptor channel block 108 a. Thedescriptor channel block 108 a increments the value of the counterspecified by the “Counter Inc” field after the descriptor channel blockhas transmitted the control information of descriptor 201 a to the DMAXassociated with the DMAD of the descriptor channel block 108 a.

“Link Addr” field helps the electronic circuits within a descriptorchannel block of a DMAD maintain a variety of data structure inhardware. “Link Addr” field identifies the DMEM location where the nextdescriptor that the descriptor channel block must process is stored.Additionally the “Link Addr” field is not programmed by the software,instead the electronic circuits of the descriptor channel block, asdescribed below, will determine the memory location of the nextdescriptor that should be processed and store the value of that memorylocation in the “Link Addr” field.

Loop address field of a control descriptor, specifically a loopdescriptor, allows the electronic circuits within a descriptor channelblock of a DMAD to implement the loop mechanism. In FIG. 2 the “LoopAddr” field of descriptor 203 a contains the memory address value ofdescriptor 201 a, thereby causing the descriptor channel block of theDMAD to reprocess descriptor 201 a. After reprocessing descriptor 201 a,the descriptor channel block of the DMAD will process the descriptor ofthe memory address stored in the “Link Addr” field of descriptor 201 a,which means the descriptor channel block will reprocess descriptor 202a. Thus, the descriptor channel block will continue to reprocess all thedescriptors until the loop condition is satisfied. The loop condition indescriptor 203 a is specified by “Iteration Count”. In FIG. 2 the loopcondition is satisfied when the iteration count equals zero.

A descriptor channel block stores the iteration count specified in aloop descriptor in a particular register designated for storingiteration count values. Each time the descriptor channel block processesthe loop descriptor, the descriptor channel block reads or retrieves theiteration count value from the particular register and determineswhether it is zero or not. If the iteration count value is not zero,then the descriptor channel block processes the loop descriptor,decrements the iteration count value in the particular register by one,and, as described above, reprocesses all the descriptors linked with theloop descriptor. In FIG. 2, descriptor channel block 108 a stores theiteration count value of descriptor 203 a in a register and every timedescriptor channel block 108 a processes descriptor 203 a, descriptorchannel block 108 a retrieves the iteration count value stored in theregister and determines whether the iteration count value is zero ornot. If the iteration count value is not zero, then descriptor channelblock 108 a processes descriptor 203 a, decrements the iteration countvalue in the register, and begins reprocessing descriptor 201 a.Therefore, each descriptor in FIG. 2 will be processed 5 times.

Processing of Descriptors by DMAD

Once the descriptors 201 a, 202 a, 203 a are programmed and stored inDMEM at addresses 0x5000, 0x5010 and 0x5020, respectively, coreprocessor 103 a pushes the DMEM addresses of descriptors 201 a, 202 a,203 a into a FIFO register accessible by DMAD 106 a. In an embodiment acore processor also indicates a particular hardware data channel of adescriptor channel block of the DMAD that a descriptor should be pushedonto. The descriptor channel block of the DMAD will either add thedescriptors to an existing list maintained by the descriptor channelblock or build a new list. In building or adding to the list, thedescriptor channel block of the DMAD will write the second memoryaddress pushed on to the FIFO register to the descriptor's link addressfield of the first descriptor put on the list.

For example, in FIG. 2, memory addresses of descriptors 201 a, 202 a,203 a are pushed on to a FIFO register accessible by core processor 103a and DMAD 106 a. The memory address of descriptor 201 a is pushed infirst, then the memory address of 202 a is pushed in, and then thememory address of 203 a is pushed in. As described above, eachdescriptor channel block of a DMAD maintains two lists per hardware datachannel, an active list and a free list. Descriptor channel block 108 adetermines whether the active list of the hardware data channel ontowhich the memory addresses of descriptors 201 a, 202 a, 203 a werepushed is empty. In an embodiment, a descriptor channel block maydetermine whether a list is empty based on a counter associated with thelist. Descriptor channel block 108 a determines whether the active listis empty based on whether a counter associated with that active list iszero.

The descriptor channel block 108 a adds to the active list by writing orcopying the memory address of descriptor 202 a into the link addressfield of descriptor 201 a and the memory address of descriptor 203 ainto the link address field of descriptor 202 a. If the active list ofthe hardware data channel controlled by descriptor channel block 108 ais not empty, then descriptor channel block 108 a writes or copies thememory address of descriptor 201 a into the link address field of thelast descriptor that was pushed onto that particular hardware datachannel, before descriptor 201 a. If the active list of the hardwaredata channel is empty, then descriptor channel block 108 a copies thememory address of descriptor 201 a from the FIFO register to a registerdesignated to store the next descriptor that will be processed.

Descriptor channel block 108 a retrieves the descriptor data ofdescriptor 201 a from the DMEM using the memory address of descriptor201 a. Descriptor channel block 108 a determines whether a waitcondition needs to be satisfied by checking the WAIT field of thedescriptor. In FIG. 2, a WAIT condition is required to be satisfied andis controlled by the value of Event0. Descriptor channel block 108 adetermines whether the wait condition is satisfied by determining thevalue of Event0. In an embodiment, a descriptor channel block maydetermine the value of an event by checking a register comprising valuesof all events that the descriptor channel block may use or is programmedto use. A WAIT condition is satisfied if the event specified by the WAITfield is at the specified WAIT value. Once, the WAIT condition issatisfied, a descriptor channel block does not have to wait any longerto process the descriptor.

In response to determining that the WAIT condition is satisfied,descriptor channel block 108 a continues with the processing of thedescriptor and determines the type of the descriptor. In an embodiment,the descriptor channel block determines the type of the descriptor basedon an encoded value in the “Desc Type” field. In FIG. 2, descriptor 201a is a read descriptor where the source memory is the DDR memory and thedestination memory is the DMEM local to core processor 103 a or DMEMunit 102 a. Descriptor channel block 108 a transmits the controlinformation of descriptor 201 a, including the value for the “Src AutoInc Allow” field, the source counter value, since the “Src Auto IncAllow” field value is set, and any other information that may be neededto perform any of the operations specified in the descriptor to the readdescriptor interface of DMAD 106 a. In an embodiment, descriptor channelblock 108 a may transmit fragments of the control information of adescriptor and any other data needed to perform any of the otheroperations specified in the descriptor to the read descriptor interfaceof DMAD 106 a. The size of each of the fragments depends on the width ofthe bus interface connecting descriptor channel block 108 a with theread descriptor interface of DMAD 106 a. Descriptor channel block 108 aalso determines whether the source address specified in the descriptorneeds to be adjusted or modified based on the “Src Auto Inc Allow”field.

A descriptor channel block may use one or more values of the fields ofthe descriptor to determine whether or not the source address needs tobe automatically adjusted or modified. In FIG. 2 descriptor channelblock 108 a determines that the source address needs to be automaticallyadjusted or modified based on the value of the “Src Auto Inc Allow”field. Descriptor channel block 108 a also determines whether the valueof the counter specified in the “Counter Inc” field should beincremented based on the value of the “Src Addr Inc” field. The counterspecified by the “Counter Inc” field of descriptor 201 a is the “src”counter. Thus, descriptor channel block 108 a also transmits to the readinterface of DMAD 106 a, the counter value of the “src” counter. Eachhardware data channel is associated with a particular counter used inadjusting or modifying a source address, which is stored in a registerand a managed by the descriptor channel block controlling the hardwaredata channel. The “src” counter in example of FIG. 2 is the counterassociated with the hardware data channel controlled by descriptorchannel block 108 a. In FIG. 2, the “src” counter value is zero thefirst time it is transmitted. Descriptor channel block 108 a, aftertransmitting the value of the “src” counter to the read descriptorinterface of DMAD 106 a, increments the value of “src” counter by 1.

A descriptor channel block is also associated with a destination countervalue. The destination counter value is incremented in a similar manneras the source counter value, except that the value of the “Dest AddrInc” field determines whether the destination counter will beincremented and the value of the “Dest Auto Inc Allow” field determineswhether the destination address specified in the descriptor should bemodified by an offset value. The “Counter Inc” field will specify orindicate the destination counter associated with the descriptor channelblock.

Processing of Descriptor by DMAX

Descriptor 201 a data is transmitted to the arbitration unit 112 a andthen stored in the FIFO register 112 b. FIFO register 112 b thentransmits the data to read descriptor parser logic block 121 b and theninto a register within the read descriptor parser logic block 121 b. Inan embodiment, if descriptor data is transmitted in fragments, then adescriptor parser logic block reassembles the descriptor data.

Processing of Descriptor by DMAC

Descriptor read descriptor parser logic block 121 b determines whetherthe source address specified in the descriptor data should be adjustedbased on a value corresponding to an auto increment of source addressfield. In FIG. 2, “Src Auto Inc Allow” is such a field and based on thevalue of that field, read descriptor parser logic block 121 b determinesthat the source address should be automatically adjusted or modified. Inan embodiment, source address may be automatically adjusted or modifiedaccording to the following formula:New Source Address=source address+source address countervalue*rows*column width(size in bytes)

The source address above is the source address transmitted in thedescriptor data. The counter value is the value of the counter that wastransmitted along with the descriptor data, which in example of FIG. 2is zero. The rows are the number of rows specified in the descriptordata and column width is the size of the column in bits. Therefore,plugging corresponding values into the above formula results in:=0x0 0000 0000+0*1000*8=0x0 0000 0000

The New Source Address above is the same as the source address specifiedin the descriptor data since the value of the counter that helpsdetermine the offset from the source address is zero. This is anaccurate result because descriptor 201 a represents the first 1000 rowsof the 10,000 rows of data that are required to be processed in FIG. 2,therefore, an offset from the initially specified address is notrequired. Read descriptor parser logic block 121 b transmits the controlinformation of descriptor 201 a and any other data required to performany operations specified in descriptor 201 a to an appropriate loadengine block of data movement engine 130 a based on the direction of thedata movement indicated in the descriptor type field of a descriptor. InFIG. 2, the descriptor type field, “Desc Type”, indicates that the datamovement is from DDR to DMEM, therefore, the appropriate load engineblock to which the control information of descriptor 201 a and any otherdata required to perform any operations specified in descriptor 201 a istransmitted is a DDR load engine block of data movement engine 130 a.

The appropriate load engine block of a data movement engine determinesthe type of the source memory specified in the descriptor data andgenerates a read request based on the type of source memory. In FIG. 2,in response to determining that the source memory is DDR memory, the DDRload engine block of data movement engine 130 a generates a read requestto the system bus interface master block 123. In an embodiment, theamount of data requested in a read request may have a maximum threshold,and the number of read requests generated by an appropriate load engineblock of a data movement engine may be based partly on the maximumthreshold on the amount data that can be requested within one readrequest and the amount of data that a descriptor is requesting for initeration of its processing. For example, if the maximum threshold is256 bytes, then the appropriate load engine block of data movementengine 130 a will generate 32 read requests to satisfy the 8000 bytes ofdata requested by descriptor 201 a.

System bus interface master block 123 accepts the read requests andtransmits the read requests to the appropriate memory unit interfacethat can accept the requests. In response to the requests, datacorresponding to the read requests are returned to the system businterface master block 123. Data corresponding to the read requests istransmitted from the system bus interface master block 123 to theappropriate load engine of the data movement engine that initiated theread requests. The appropriate load engine of the data movement enginetransmits the data to an appropriate storage block unit within the datamovement engine based on the destination memory unit indicated in thedescriptor type field of the descriptor. In the example of FIG. 2,system bus interface master block 123 transmits the data to the DDR loadengine of data movement engine 130 a, and the DDR load engine transmitsthe data to the DMEM storage block unit within data movement engine 130a. DMEM storage block unit within data movement engine 130 a transmitsthe data and control information of the descriptor to FIFO register 114b within DMAX 110 a along with the destination address specified indescriptor 201 a and an identifier associated with core processor 103 a.FIFO register 114 b identifies, using the core processor identifierincluded in the control information transmitted to FIFO register 114 bfrom the DMEM storage block unit, DMEM unit 102 a as the DMEM unitassociated with the core processor identifier, and transmits data fromwrite interface 114 a to DMEM unit 102 a via DMEM interface block 107 awithin DMAD 106 a to store the data at the destination address specifiedin the descriptor.

Data Manipulation Operations

In an embodiment, descriptor 201 a may indicate that one or more tabulardata manipulation operations, such as a gather, a scatter, agather-scatter, or striding operations, may need to be performed on thetabular data requested from the source memory location.

Gather Operation

A gather operation is a type of filtering operation wherein transfer ofa row within a column of tabular data is dependent upon whether theparticular row satisfies filtering criteria.

A bit vector or a list of row identifiers are used to evaluate whetherthe particular row satisfies the filtering criteria. In someembodiments, a high bit within a bit vector indicates that thecorresponding row within the column of tabular data should betransferred to the destination memory location. For example, if the bitvector is 1011, then the first, third and fourth rows within the columnof tabular data should be transferred to the destination memorylocation. In some embodiments, a list of row identifiers may point tothe exact rows within the column of tabular data that can be transferredto the destination memory location. Therefore, filtering of tabular datafrom a source memory location is performed prior to storing the tabulardata in a destination memory location.

Scatter Operation

A scatter operation allows for tabular data to be stored at non-lineardestination addresses. In an embodiment, a scatter operation uses a bitvector or a list of row identifiers and the base destination address todetermine the destination address for each row of column of tabular databeing transferred to the destination memory location. A gather and ascatter operation, referred herein as a gather-scatter operation, mayalso be performed in combination.

Gather-Scatter Operation

In a gather-scatter operation, tabular data from the source memorylocation is filtered while the data is in-flight to the destinationaddress, as described above, and the resulting data is stored within thedestination memory in non-linear addresses. In an embodiment, use of agather and a scatter operation ensures that each row of column oftabular data that satisfied the filtering criteria is stored in thedestination memory in a manner such that the memory address offsetbetween one filtered row of column of tabular data to another filteredrow of column of tabular data mirrors the source memory address offset.

Stride Operation

A striding operation allows for tabular data to be converted from acolumn major format in a source memory to a row major format in adestination memory. The striding operation also allows for convertingdata from row major format in the destination memory to column majorformat in the source memory. To perform a conversion from column majorto row major, a stride is determined based on the number of bytes perrow of all interested columns of tabular data. The interested columns oftabular data will belong to a particular data table.

The data movement system, described herein, determines the destinationaddress for each row of a column of tabular data using the basedestination address specified in the descriptor and the stride. Toperform a conversion from row major in destination memory in order tostore it in column major format in source memory, the data movementsystem uses the stride to determine all the rows of a column of tabulardata. For example, to determine the second row of a column of tabulardata, the data movement system uses the stride amount to offset from theaddress of the first row of column of data stored in the destinationmemory in a Row Major format. Thus the particular format in whichtabular data is stored in a source memory will not provide compatibilityissues in processing that data.

Transmission of Tabular Data to Destination Memory

After transmitting data to FIFO register 114 b, the DMEM store unit indata movement engine 130 a transmits the descriptor return path ofdescriptor 201 a to descriptor return block in DMAC 140, whereindescriptor return path of a descriptor includes a DMAD identifier, adescriptor channel block identifier and a descriptor identifierassociated with the descriptor. Descriptor return block in DMAC 140transmits the descriptor return path of descriptor 201 a to a returneddescriptor FIFO register within FIFO register 114 b. FIFO register 114 btransmits the descriptor return path of descriptor 201 a to descriptorchannel block 108 a in DMAD 106 a. Descriptor channel block 108 a setsthe notify event to signal to the core processor 103 a that datarequested by descriptor 201 a is ready to be processed. In FIG. 2, thenotify event is identified by the “Notify” field of descriptor 201 a,and is Event0.

Descriptor Return Path

Prior to processing a descriptor, a descriptor channel block determineswhether there are any free or available descriptor identifiers that canbe associated with the descriptor. If the descriptor channel blockdetermines that no descriptor identifiers are available, then thedescriptor channel block waits until a descriptor identifier isavailable. In an embodiment, one or more registers comprise all freedescriptor identifiers. Once a descriptor identifier is available, thedescriptor channel block begins processing a descriptor and associatesthe available descriptor identifier with the descriptor. In someembodiments the descriptor identifier may be a 2 bit identifier,therefore, each descriptor channel block within a DMAD may process andsupport up to four different descriptors at a time. The descriptoridentifier associated with the descriptor is included within the controlinformation of that descriptor and transmitted to the DMAC.

Additionally, the descriptor channel block includes its own identifierwithin the control information transmitted to the DMAC. In someembodiments, the descriptor channel block identifier is a one bitidentifier. For example a value of zero in that bit identifies onedescriptor channel block of a DMAD and a value of one in that bitidentifies the other descriptor channel block of the DMAD. Descriptorchannel block also includes a DMAD identifier associated with the DMADwithin which the descriptor channel block resides. In some embodiments,the DMAD identifier may be 5 bits.

The descriptor identifier, the descriptor channel block identifier andthe DMAD identifier is collectively referred to herein as the descriptorreturn path. In some embodiments, the identifier associated with thedescriptor may be a sequence of bits, and different subsets of thesequence of bits correspond to the descriptor identifier, the descriptorchannel block identifier, and the DMAD identifier. For example, theidentifier associated with the descriptor may be a sequence of 8 bits,where the five most significant bits correspond to the DMAD identifier,the next bit corresponds to the descriptor channel block identifier andthe least significant two bits correspond to the descriptor identifier.

Once the DMAC completes processing all the operations necessary tosatisfy the data requests specified in a descriptor, then the DMACconfigures a descriptor return path for that descriptor. The descriptorreturn path of that descriptor includes the DMAD identifier, thedescriptor channel block identifier and the descriptor identifierassociated with the descriptor and included in the control informationof that descriptor. The DMAC transmits the descriptor return to itsoriginating DMAD via the DMAX associated with the originating DMAD. Arouting unit within the DMAX associated with the originating DMADdetermines the originating DMAD based on the DMAD identifier included inthe descriptor return path and transmits the descriptor return path tothe descriptor return interface block of the originating DMAD.

The descriptor return interface block of the originating DMAD determinesthe descriptor channel block that processed that descriptor based on thedescriptor channel block identifier and transmits the descriptor returnpath to the descriptor channel block that processed that descriptor. Thedescriptor channel block that processed that descriptor determines,based on the descriptor identifier, the DMEM location of thatdescriptor. In an embodiment, the association between a DMEM location ofa descriptor and the descriptor identifier associated with thedescriptor is stored in a lookup table by the descriptor channel blockthat processed the descriptor.

Descriptor channel block 108 a determines whether the loop count iszero, and if the loop count is zero, the descriptor channel block 108 adetermines whether descriptor 201 a will be added to the free list ofthe hardware data channel controlled by descriptor channel block 108 a.In an embodiment, the descriptor channel block 108 a may determinewhether or not a descriptor will be added to the free list based onwhether data of the descriptor indicates that the particular descriptorshould be added to the free list. For example, there may be a free pushfield within the data of the descriptor that may have a value of 1 or 0to indicate that the particular descriptor should be added to the freelist. Additionally, if the loop count is zero, then the descriptorchannel block 108 a also decrements the active count value of thatchannel by 1. If the loop count is not zero, then descriptor channelblock 108 a terminates the processing of descriptor 201 a for thisparticular iteration.

Traversing the Hardware Managed List

After descriptor channel block 108 a transmits descriptor 201 a data toarbitration unit 112 a, descriptor channel block 108 a determines DMEMunit 102 a address of the next descriptor within the active list of thedescriptor channel block based on the link address field within the dataof descriptor 201 a. Descriptor channel block 108 a retrieves data ofdescriptor 202 a from DMEM 102 a address 0x5010. Descriptor channelblock 108 a processes descriptor 202 a similarly to how descriptor 201 ais processed and transmits descriptor 202 a data to arbitration unit 112a along with the “src” counter value, as indicated by descriptor 202 a.The “src” counter value, when transmitted with the data of 202 a, is 1.After descriptor 202 a data is transmitted to arbitration unit 112 a,descriptor channel block 108 a increments “src” counter value by 1.Thus, the “src” counter value is now 2.

Descriptor 202 a control information and the “src” counter valuetransmitted along with descriptor 202 a data is stored in FIFO register112 b and then transmitted to read descriptor arbitration unit 121 a andstored in read descriptor parser logic block 121 b. Read descriptorparser logic block 121 b again determines, similar to the way describedabove, that the source address specified in the descriptor data shouldbe adjusted or auto incremented. Read descriptor parser logic block mayadjust or modify the source address according to the same formuladescribed above, which is:New Source Address=source address+source counter value*rows*columnwidth(size in bytes)

The source address above is the source address transmitted in descriptor202 a data. The counter value is the value of the counter that wastransmitted along with descriptor 202 a data, which is 1. The rows arethe number of rows specified in descriptor 202 a data and column widthis the size of the column in bytes. Therefore, plugging thecorresponding values into the above formula results in:=0x0 0000 0000+1*1000*8=0x0 0000 1F40

The New Source Address is now 0x0 0000 1F40, wherein 1F40 is thehexadecimal value equivalent to 8000. This is an accurate result becausedescriptor 202 a represents the second 1000 rows of the 10,000 rows ofdata that are required to be processed in FIG. 2, therefore, an offsetfrom the initially specified address is required. Read descriptor parserlogic block 121 b transmits the descriptor data to the appropriate loadengine block of data movement engine 130 a. The appropriate load engineblock of data movement engine 130 a processes descriptor 202 a datasimilar to the processing of descriptor 201 a data. Data retrieved fordescriptor 202 a is stored in DMEM 102 a at the destination memoryaddress specified in descriptor 202 a.

DMEM 102 a address of descriptor 202 a is transmitted from descriptorreturn block of DMAC 140 to descriptor channel block 108 a of DMAD 106 asimilar to the way DMEM 102 a address of descriptor 201 a wastransmitted above. Descriptor channel block 108 a sets notify event tosignal to the core processor 103 a that data requested by descriptor 202a is ready to be processed. In FIG. 2, the notify event identified bythe “Notify” field of descriptor 202 a is Event1. Descriptor channelblock 108 a again determines whether the loop count is zero and if it iszero, then descriptor channel block 108 a completes processing ofdescriptor similar to the way described above for descriptor 201 a. Ifthe loop count is not zero, then descriptor channel block 108 aterminates the processing of descriptor 202 a for this particulariteration.

Hardware Implemented Looping Mechanism

After descriptor channel block 108 a transmits descriptor 202 a data toarbitration unit 112 a, descriptor channel block 108 a determines DMEM102 a address of the next descriptor within the active list of thedescriptor channel block based on the link address field of descriptor202 a. Descriptor channel block 108 a retrieves data of descriptor 203 afrom DMEM 102 a address 0x5020. Descriptor channel block 108 adetermines that descriptor 203 a is a program or control type descriptorand in particular a loop type descriptor. Descriptor channel block 108 adetermines whether the loop count or iteration count is zero and if itis not zero, then descriptor channel block 108 a decrements the loopcount value by 1. As described above, the loop or iteration count isstored in a particular register designated for storing loop count valuesand the descriptor channel block retrieves the loop count value from theparticular register and determines whether the loop count value is zeroor not. If the loop count is not zero, then the descriptor channel blockupdates the loop count by decrementing the loop count value by 1 andstores the updated loop count value in the particular register. In FIG.2, the iteration count value starts at 4, therefore, the first timedescriptor 203 a is processed, the loop or iteration count is 4 andafter it is decremented by descriptor channel block 108 a, the loop oriteration count will be 3.

In response to determining that the loop or iteration count is not zero,descriptor channel block 108 a determines which descriptor it shouldloop back to and reprocess. Descriptor channel block 108 a determineswhich descriptor it should loop back to based on descriptor 203 aspecifying a loop back address that identifies the DMEM address of thedescriptor that should be processed again. In FIG. 2, the loop backaddress is specified in the “Loop Addr” field of descriptor 203 a andDMEM 102 a address of 0x5000 is the address of descriptor 201 a withinthe DMEM 102 a.

Descriptor channel block 108 a retrieves descriptor 201 a data from DMEM102 a. Descriptor channel block 108 a determines whether the waitcondition of descriptor 201 a is satisfied based on value of eventEvent0. In FIG. 2, the wait condition of descriptor 201 a is satisfiedif Event0 value is 0. As described above, descriptor channel block 108 apreviously set the value of Event0 to 1 in order to indicate to coreprocessor 103 a that data is available for processing at the destinationaddress specified by descriptor 201 a. Therefore, if core processor 103a did not complete its processing of the data at the destination addressspecified by descriptor 201 a, then the core processor will not clearEvent0 to 0, hence descriptor channel block 108 a must wait until theEvent0 value is cleared to 0, i.e. set to 0.

If Event0 value is cleared to 0, then descriptor channel block 108 aprocesses descriptor 201 a similar to the way descriptor 201 a wasprocessed in the previous iteration, described above. Descriptor channelblock 108 a continues to traverse the active list of the hardware datachannel and based on the link address data of descriptor 201 a retrievesdescriptor 202 a data. Descriptor channel block 108 a processesdescriptor 202 a similar to the way it was processed in the previousiteration. Descriptor channel block 108 a continues to traverse theactive list of the hardware data channel and based on the link addressdata of descriptor 202 a retrieves data of descriptor 203 a.

Descriptor channel block 108 a again determines whether the loop countis 0. Loop count value is 3, therefore, descriptor channel block 108 adecrements the loop count value by 1 and again loops back to descriptor201 a and processes descriptor 201 a again. Descriptor channel block 108a continues to loop through the descriptors until the loop count valueis 0. When the loop count value is 0, descriptor channel block 108 adetermines whether source or destination counters of the descriptorchannel block 108 a should be reset. In FIG. 2, descriptor 203 aspecifies, with “Src Count Reset” and “Dest Count Reset”, fields thatsource and destination counters of hardware data channel must be reset.

Descriptor channel block 108 a notifies core processor 103 a that theloop has terminated or finished by setting the value of Event30 to 1since Event30 is specified in descriptor 203 a as the event that thecore processor is configured to receive a notification from fordescriptor 203 a. Descriptor channel block 108 a also decrements theactive list count of the hardware data channel by 1. Processing ofdescriptor 203 a is now complete and consequently processing ofdescriptors 201 a and 202 a. Thus, 10,000 rows of data from a sourcememory location have been processed by the data movement system.

Moving a Data Table Using Descriptors

FIG. 3 illustrates an example of moving an entire data table, comprisingfour columns, from a source memory to a local DMEM using descriptors.FIG. 3 comprises four data descriptors, 310 a, 311 a, 312 a, 313 a andone control descriptor 314 a. Each descriptor represents a column ofdata of the data table stored in the source memory. Source memory inFIG. 3 is a DDR memory external to the data movement system. Destinationmemory in FIG. 3 is a DMEM, local to the core processor that programmeddescriptors 310 a, 311 a, 312 a, 313 a. For the purpose of illustratinga clear example, FIG. 3 will be described using the hardware componentsand processes described in FIG. 1 and FIG. 2. For the purpose ofillustrating a clear example, descriptors in FIG. 3 are also programmedby core processor 103 a.

Descriptor 310 a specifies the starting address of the first column ofthe data table in the source memory at the “Src Addr” field ofdescriptor 310 a. Similarly, descriptors 311 a, 312 a, 313 a, specifystarting addresses of the second, third and fourth columns of the datatable in the source memory as their respective source addresses. Each ofthe descriptors 310 a, 311 a, 312 a, 313 a specify a differentdestination address within DMEM 102 a, the DMEM local to core processor103 a. Descriptor 314 a is a loop descriptor which indicates that thedescriptor channel block that processes these descriptors should loopback to descriptor 310 a, the descriptor that is stored at the DMEM 102a address specified in descriptor 314 a.

One of the descriptor channel blocks of DMAD 106 a will add descriptors310 a, 311 a, 312 a, 313 a, 314 a to the active list of the hardwaredata channel controlled by the descriptor channel block similar to theway descriptor channel block in FIG. 2 added descriptors to the activelist. The descriptor channel block will begin processing descriptors ofFIG. 3 with descriptor 310 a. Processing of descriptor 310 a is similarto the way descriptor processing has been described in FIG. 2 and FIG.1.

However, unlike FIG. 2, the source address counter of the descriptorchannel block will not be incremented after descriptor 310 a data istransmitted to the arbitration unit 112 a because descriptor 310 a doesnot specify that the source address counter should be incremented. Thisis accurate for FIG. 3 because source addresses of descriptors 311 a,312 a, and 313 a are different for each since each descriptor isprocessing a different column of data of the data table, each of thedescriptors 311 a, 312 a, and 313 a, in the first iteration of the loop,should process their respective column of data from the source addressspecified in the descriptor, without any offset from the source address.Similarly, descriptor 311 a, 312 a also do not specify that sourceaddress should be incremented in order to ensure that the descriptorfollowing them begins processing their respective columns of data fromthe correct memory address.

Descriptor 313 a data specifies that the source address counter shouldbe incremented. Thus, the source counter of descriptor channel block 108a is incremented after control information of descriptor 313 a istransmitted to arbitration unit 112 a. Incrementing source addresscounter after the last bytes of the control information of descriptor313 a is transmitted ensures that the next time descriptors 310 a, 311a, 312 a, 313 a are processed the source address specified in 310 a, 311a, 312 a, 313 a are adjusted, modified or offset accurately. Theremaining aspects of processing and returning descriptors 310 a, 311 a,312 a, 313 a, 314 a are similar to the way it is described in FIG. 1 andFIG. 2.

Thus, data movement system may copy an entire data table from a sourcememory and store the data table in a destination memory usingdescriptors.

Performing Data Manipulation Operations

Approaches for performing tabular data manipulation operations whilemoving data from a source memory location to a destination memorylocation are initially illustrated using a gather operation. Asdescribed earlier, a gather operation is a type of filtering operationwherein transfer of a row within a column of tabular data is dependentupon whether the particular row satisfies a filtering criteria and ascatter operation allows for tabular data to be stored at non-lineardestination addresses. Other types of tabular data manipulationsoperations will be described later.

FIG. 4 illustrates example descriptors used for performing a gatheroperation. These descriptors include a data descriptor that specifies toperform a gather operation for a column. A data descriptor may alsospecify a scatter operation. A gather or scatter operation can beperformed using several filter modes for filtering rows, one mode usinga list of row identifiers (RID) and one using a bit vector (BV).

The filter mode is specified by a value in a “scat/gat” register of aDMAD. A program descriptor is used to configure the value of a “scat/gatregister”. The value of the scat/gat register specifies not only whetherthe filter mode is RID or BV, but also the storage address of an RID orBV within the DMS memory. A RID or BV that is used to perform a gatheroperation is copied from DMEM to DMS memory, or from main memory to DMSmemory, using a data descriptor.

Referring to FIG. 4, it depicts four descriptors, program descriptor 401a, data descriptor 402 a and data descriptor 403 a, and loop descriptor404 a. For the purposes of illustration, FIG. 4 will be described usingthe hardware components and processes described in FIG. 1, FIG. 2, andFIG. 3; descriptors in FIG. 4 are also programmed by core processor 103a. The descriptors are used to perform a gather operation using a BV.

In FIG. 4, core processor 103 a configures program descriptor 401 a,which is used to configure a scat/gat register. The value of thescat/gat register specifies various aspects of performing a gatheroperation. Descriptor 401 a indicates that it is a program descriptor byspecifying in the descriptor type field a value that a DMAD decodes tobe corresponding to a program descriptor. Descriptor 401 a specifies toconfigure the scat/gat register value by specifying the scat/gatregister in the “Register” field. The value of the scat/gat registerspecifies whether RID or BV mode is being used for filtering, and if RIDmode is specified, what the width of a RID is.

Accordingly, Descriptor 401 a specifies whether RID or BV mode is beingused for filtering by specifying a particular value in the “Mode” field.In descriptor 401 a, that value specifies BV mode. If the mode had beenRID, then descriptor 401 a should have specified the width of a RID.According to an embodiment, the width of a RID may be 1, 2, 4, or 8bytes.

Descriptor 401 a also specifies the DMS memory address of where the BVshould reside. The BV may be initially formed and/or stored by coreprocessor 103 a in its DMEM unit 102 a. A separate descriptor,descriptor 402 a, specifies to move a RID or BV to this DMS memoryaddress.

Descriptor 402 a is the data descriptor in FIG. 4 that specifies to movethe BV from DMEM to DMS memory. Descriptor 402 a specifies that the BVis stored at the DMEM location specified by the “DMEM Addr” field, i.e.the source memory location. Descriptor 402 a also specifies, using the“DMS Addr” field, the destination address of where that BV is to bestored. The value in the “DMS Addr” field specifies a memory locationwithin DMS memory 150 to store the BV. Moving or copying and storing theBV (or RID) to a DMS memory reduces latency in accessing the BV (or RID)by the data movement engine while performing the gather operation. In anembodiment, Descriptor 402 a can specify to move a BV (or RID) from mainmemory or a DDR memory unit to DMS memory.

Furthermore, descriptor 402 a also indicates the length of the BV thatis to be stored in the destination memory specified in programdescriptor 401 a and 402 a. In an embodiment, the length of the BV thatis to be stored is based on the number of rows specified in theparticular descriptor that will be processed to move the BV to DMSmemory from DMEM. Descriptor 402 a also specifies in the “Rows” fieldthe number of bits that particular bit vector comprises.

In FIG. 4, descriptor 403 a is a data descriptor that specifies a gatheroperation to be performed on a column of tabular data. Descriptor 403 aspecifies within the “Gather” field that a gather operation should beperformed. In an embodiment, the value within the “Gather” field may bean encoded value such as a bit or binary number that indicates to adescriptor channel block within a DMAD that a gather operation is beingrequested to be performed on the column of tabular data. The otherfields of descriptor 403 a are similar to the fields of the descriptorsdescribed in FIG. 2 and FIG. 3, and similar to descriptors processed bythe DMS shown in FIG. 1.

Descriptor 404 a is a loop descriptor. It is configured and processedsimilarly as described for loop descriptor 314 a.

Processing Gather Operation

In FIG. 4, elements 401 b, 402 b, 403 b and 404 b each correspond tooperations performed for descriptors 401 a, 402 a, 403 a, and 404 a,respectively. The purpose of these elements is to depict the order ofoperations performed for descriptors 401 a, 402 a, 403 a, and 404 a.

Core processor 103 a configures descriptors 401 a, 402 a, 403 a, and 404a, and transmits the respective memory locations within DMEM unit 102 ato one of descriptor channel blocks in DMAD 106 a. For example, coreprocessor 103 a may transmit an identifier associated with descriptorchannel block 108 a along with the memory location of descriptor 401 ato a FIFO interface within DMAD 106 a. DMAD 106 a, based on theidentifier received, adds descriptor 401 a to the active list ofdescriptor channel block 108 a. The other descriptors 402 a, 403 a, and404 a are processed similarly. Retrieval of descriptors 401 a, 402 a,403 a, and 404 a are performed in the same manner as described inrelationship to FIG. 1, FIG. 2 and FIG. 3.

In FIG. 4, descriptor channel block 108 a decodes descriptor 401 a andidentifies descriptor 401 a as a program descriptor based on thedescriptor type field of descriptor 401 a. Since the descriptor 401 aidentifies the register to configure as the scat/gat register, thedescriptor channel block 108 a configures scat/register of DMAD 106 a toa value that specifies that the filtering mode is BV, and the address inDMS 150 of where the BV will be stored.

In FIG. 4, descriptor channel block 108 a decodes descriptor 402 a andidentifies descriptor 402 a as a data descriptor based on the descriptortype field of descriptor 402 a. As described above, the descriptor typefield of a data descriptor also indicates the direction of datamovement, thus identifying the source memory location, from where datais to be moved or copied from, and a destination memory location, towhere the data is to be stored. Descriptor type field of descriptor 402a indicates that the direction of data movement is from DMEM to a memoryunit in DMS memory, therefore, the memory location specified in the“DMEM addr” field is the source memory location of data within the DMEMunit 102 a and the memory location specified in the “DMS addr” field isthe destination memory location within DMS memory unit used for storingthe BV.

Routing unit 114 a transmits the read request, based on the controlinformation of descriptor 402 a, to the DMEM interface block 107 a. DMEMinterface block 107 a retrieves the BV from DMEM unit 102 a, based onthe memory location specified in the “DMEM Addr” field of descriptor 402a. The control information received at DMEM interface block 107 aincludes the memory location specified in the “DMEM Addr” field ofdescriptor 402 a. DMEM interface block 107 a generates a read responsecomprising the BV from DMEM unit 102 a and control information ofdescriptor 402 a. DMEM interface block 107 a transmits the read responseto arbitration unit 113 a. Arbitration unit 113 a, based on the controlinformation of descriptor 402 a, transmits the read response to datamovement engine 130 a.

Data movement engine 130 a stores the BV at the memory locationspecified in the “DMS Addr” field of descriptor 402 a in the memory unitof the DMS used for storing row identifiers or BVs.

Processing of descriptors that specify data manipulation operations thatuse the BV and that follows a descriptor that stores the BV in a memoryunit in DMS may be temporarily suspended until all of the required BV issuccessfully stored in the memory unit in the DMS, thereby preventinggeneration of read or write requests using an incomplete BV for thedescriptors that specify the data manipulation operations.

The descriptor channel block may temporarily suspend processing ofdescriptors that follow the current descriptor that is being processed,based on the type of wait event and wait conditions specified in thecurrent descriptor. One type of wait event, referred to herein as a“pre-wait” event, is a wait event that indicates to the descriptorchannel block that the processing of the descriptor that specified thatevent type should not begin until the wait condition, also specified inthat descriptor, is satisfied. An example of this type of wait event isdescribed in FIG. 2 and FIG. 3 above. Another type of wait event,referred to herein as “post-wait” event, is a wait event that indicatesto the descriptor channel block that the descriptor specifying thepost-wait event type can be processed, however that the descriptorchannel block cannot begin processing the next descriptor in the activelist of that descriptor channel block until the wait condition specifiedin the descriptor with the post-wait is satisfied and that the operationthe descriptor is performing has completed.

FIG. 4 illustrates the use of the post-wait event to temporarily suspendprocessing of the other descriptors in the active list of the descriptorchannel block. In FIG. 4, descriptor 402 a specifies that the event typeis a post-wait event, therefore descriptor channel block 108 a, thedescriptor channel block processing descriptor 402 a, temporarilysuspends processing of the next descriptor until the post-wait conditionspecified in descriptor 402 a is satisfied. As described above, apost-wait condition is satisfied if the event specified in the “WAIT”field of the descriptor is at the value specified in the “WAIT” field ofthe descriptor and the operation specified by the descriptor has beencompleted. In FIG. 4, the post-wait condition of descriptor 402 a issatisfied when the value of Event4 is set to 1. Therefore, descriptorchannel block 108 a, the descriptor channel block processing descriptor402 a, does not begin processing of the next descriptor on the activelist of descriptor channel block 108 a, descriptor 402 b, until thevalue of Event4 is set to 1. Thus, all descriptors after descriptor 402a in the active list of descriptor channel block 108 a are temporarilysuspended until the wait condition of the post-wait event of descriptor402 a is satisfied and the operation specified by descriptor 402 a,movement of the BV from DMEM to DMS memory, has completed.

Once the wait condition of descriptor 402 a is satisfied, descriptorchannel block 108 a traverses its active list as described inrelationship with FIG. 2 and FIG. 3, and begins processing descriptor403 a. Descriptor channel block 108 a determines, based on thedescriptor type field, that descriptor 403 a is a data descriptor andthat the direction of data movement is from an external memory into DMEMunit 102 a. Descriptor channel block 108 a also determines that a gatheroperation should be performed on the tabular data being stored into theDMEM unit 102 a.

As described above, the data movement system performs data manipulationoperations, such as a gather operation on the tabular data, prior tothat tabular data being stored in the destination memory unit.Therefore, the data movement engines in DMAC 140 will perform the gatheroperation requested by descriptor 403 a on the tabular data retrievedfrom the source memory location prior to any of the tabular data beingstored in the destination memory unit of the destination memory locationspecified in descriptor 403 a.

Descriptor channel block 108 a transmits the control information ofdescriptor 403 a including the gather operation specified in descriptor403 a to arbitration unit 112 a. Arbitration unit 112 a, based on thedescriptor type of descriptor 403 a, transmits control information ofthe scat/gat register of DMAD 106 a, the gather operation specified indescriptor 403 a, and an identifier associated with DMAX 110 a to readdescriptor parser block 121 b via read descriptor arbitration unit 121a.

As described above, one or more data movement engines may be associatedwith one or more DMAX units such that the read descriptor or writedescriptor parsers of a DMAC will transmit the descriptor controlinformation including any data manipulation operations specified in thedescriptor received from the one or more DMAX units to the associateddata movement engines. In FIG. 1, data movement engine 130 a isassociated with DMAX 110 a for most data movement descriptors,therefore, read descriptor parser 121 b or write descriptor parser 120 btransmit the descriptor control information including any datamanipulation operations specified in the descriptor received from DMAX110 a to data movement engine 130 a.

Read descriptor parser 121 b, based on the received DMAX identifier,transmits control information from scat/gat register of DMAD 106 a, thegather operation specified in descriptor 403 a, and an identifierassociated with DMAX 110 a to data movement engine 130 a since datamovement engine 130 a is associated with DMAX 110 a.

A data movement engine determines that data manipulation operations areto be performed on the tabular data that is being moved or copied fromthe source memory location based on the descriptor information receivedfrom either a read descriptor parser or a write descriptor parser. InFIG. 1, data movement engine 130 a, retrieves the BV stored in thememory unit of DMS, designated for storing the BV, at the memorylocation specified in the “DMS Addr” in control information from thescat/gat register as detailed in the sequence shown in FIG. 4. Thiscontrol information also informs data movement engine 130 a that thefiltering mode is BV.

Data movement engine 130 a parses the retrieved BV in order to determinewhether a read request to the source memory should be generated. Asdescribed above, each bit within a bit vector corresponds to a row inthe column of tabular data stored at the source memory location in thesource memory unit. The value of each bit identifies whether thecorresponding row in the column of tabular data may be stored in thedestination memory unit or whether it may be filtered out, thus notstored in the destination memory unit. In an embodiment, a row in acolumn of tabular data will be stored in a destination memory unit ifthe value of the corresponding bit in the BV is a 1 and a row in acolumn of tabular data will be filtered out if the value of thecorresponding bit in the BV is a 0.

In an embodiment, a data movement engine parses the BV to determinewhether values of a sufficient number of consecutive bits indicate thattheir corresponding rows will be filtered out such that a read or writerequest for their corresponding rows is not generated. The data movementengine checks whether the total cumulative size of data from thecorresponding rows exceeds a threshold size of data in determiningwhether a read or write request for the corresponding rows should begenerated. In determining the total cumulative size of data from thecorresponding rows, a data movement engine may calculate the cumulativesize using the column width of the column of tabular data, specified inthe descriptor and transmitted to the data movement engine, and thenumber of bits that indicate that their corresponding rows will befiltered out. By using a threshold size of data in part to determinewhether a read or write request should be used allows the data movementsystem to provide a flexible process of determining read or writerequests for a particular set of rows within a column of tabular data.

The threshold size of data may depend in part on the amount of data perread or write request that can be transmitted from a source memorylocation. For example, if the amount of data that can be transmitted perread or write request is 256 bytes, then the threshold amount of datamay be set to 256 bytes and a data movement engine may not generate aread request if a consecutive number of bits that indicate that theircorresponding rows should be filtered out multiplied by the column widthequal or exceed 256 bytes. The data movement engine may skip thegeneration of a read request for the rows corresponding to that set ofconsecutive number of bits and generate read or write requests for therows corresponding to the remaining number of bits in the bit vector.Consequently, the number of read or write requests generated by a datamovement engine when a gather operation is specified depends on theconsecutive number of bits that indicate that their corresponding rowswill be filtered out and not simply on the number of rows specified in adescriptor.

In FIG. 4, descriptor 403 a specifies the column width is 8 bytes, andif the threshold amount of data is 256 bytes, then data movement engine130 a may determine that a read request will not be generated if thevalues of 32 consecutive bits in the retrieved BV indicate that theircorresponding rows in the column of tabular data should be filtered out.Thus, data movement engine 130 a generates read requests based on thevalues of the bits in the BV data. Data movement engine 130 a transmitsthe read requests and control information of descriptor 403 a to systembus interface master block 123. System bus interface master block 123stores the control information of descriptor 403 a in a register withinsystem bus interface master block 123.

System bus interface master block 123 transmits the received readrequests to the source memory unit. For each read request, system businterface master block 123 receives data from source memory unit. Systembus interface master block 123 transmits the column of tabular data fromthe source memory unit and the control information of descriptor 403 ato data movement engine 130 a. Data movement engine 130 a, based atleast in part on the received gather operation and/or controlinformation of descriptor 403 a from system bus interface master block123 transmits the column of tabular data to a gather operation engine.

The gather operation engine, based on the BV, determines whether thecorresponding row within the received column of tabular data should bestored in the destination memory unit. For each bit in the BV, thegather operation engine, based on the value of the bit, determineswhether the corresponding row should be stored in the destination memoryunit. The gather operation engine identifies the corresponding row of abit within the column of tabular data based on the following:Gather address=Descriptor source base address+(column width*bit number)

The gather address given above represents the address of the rowcorresponding to the bit number. The descriptor source base address isthe source memory location specified in descriptor 403 a. The columnwidth is the size of the column in bytes and bit number represents a bitwithin the BV and bit number starts from zero. For example, if the BV iscomprised of four bits, 1011, then bit number zero is the first bit fromthe right and has value of one. Bit number one is the second bit fromthe right and has a value of one. Bit number two is the third bit fromthe right and has a value of zero. Bit number three is the fourth bitfrom the right and has a value of 1.

In an embodiment, the gather operation engine stores data gatheredfromsource addresses where the values of the bits of bit numbers are 1.The gather operation engine transmits the data of the rows withcorresponding bit values of 1 to the DMEM store engine. The gathereddata is accumulated and stored in a contiguous memory range in thedestination memory. The data of the rows is transmitted to DMEM unit 102a as described in relationship to FIG. 1, FIG. 2, and FIG. 3.

Scatter Operation

Similar to the gather operation, a descriptor may specify a scatteroperation. Data received from a source memory location is transmitted tothe scatter operation engine. The BV is also transmitted to the scatteroperation engine. The scatter operation engine determines thedestination address for each row of column of tabular data according tothe following:Scatter address=Descriptor destination base address+(column width*bitnumber)

The scatter address above represents the destination address of whereeach qualifying row of the column of tabular data will be stored. Thedescriptor destination base address is the address specified in thedescriptor. The column width is the size of the column in bytes and bitnumber represents a bit within the BV where the bit number starts fromzero.

A descriptor may specify, both, a gather and a scatter operation toindicate that a gather operation should be performed on the data fromthe source memory location and that a scatter operation should beperformed on the data upon which a gather operation is performed. Thefunctionality of the gather and the scatter operations when, both, agather and a scatter operation are specified is similar to the waydescribed above for the gather operation and for the scatter operation.

Striding Operation

A group of descriptors (one per column) may specify that a stridingoperation should be performed on a group of columns of tabular data fromtheir source memory location to their destination memory location. Thestriding operation as described above transforms the columns of tabulardata stored in column major format at the source memory location to rowmajor format at the destination memory location or columns of tabulardata stored in row major format at the source memory location to columnmajor format at the destination memory location.

A core processor may determine a stride amount to help transform from acolumn major format to a row major format or vice versa. The strideamount is the number of bytes per row across all columns of tabular datathat are of interest. For example, if two columns of tabular data are tobe moved or copied from an external memory unit and stored into a DMEMunit, then the stride amount is the sum of the column widths of bothcolumns of tabular data.

Data from the source memory location is transmitted to the strideoperation engine and the stride operation engine transforms tabular datastored in a column major format to a row major format according to thefollowing:destination address=destination base address+(dst count*stride)

The destination address above represents the destination address in DMEMand the destination base address represents the destination addressspecified in the descriptor. Dst count represents the row number of thecolumn element being moved and stride represents the stride amount inbytes. Thus each row of tabular data from the source memory stored incolumn major format will be stored at the destination memory in rowmajor format.

The stride operation engine may transform tabular data stored in a rowmajor format to a column major format according to the following:source address=source base address+(src_count*stride)

The source address above represents the source address in DMEM, and thesource base address represents the source address specified in thedescriptor. Src count represents the row number of the column elementbeing moved and stride represents the stride amount in bytes. Thus eachrow of tabular data stored in row major format at a source memorylocation will be stored at the destination memory in column majorformat.

Aligned Run Length Encoding (ARLE) Operation

The data movement system described herein allows for encoded orcompressed data from a source memory location, such as main memory or aDDR memory unit, to be decompressed prior to storing the data in thedestination memory unit, such as a DMEM unit, and for un-encoded ordecompressed data from a source memory location, such as a DMEM unit, tobe compressed prior to storing the data in main memory or a DDR memoryunit.

Compression and decompression of tabular data is performed on the fly,based on values specified in certain fields of a descriptor. Compressionand decompression of a column of tabular data are performed based on acorresponding run and data array. A run comprises one or more elements,where each element specifies how many times a corresponding data elementof a data array is repeated. Compression takes an uncompressed column ofdata and generates a data array and a corresponding run array;decompression takes a run array and a data array and generates anuncompressed column of data. When decompressing ARLE compressed data,the DMS logic reads the data and run arrays from main memory and storesthem in internal DMS memory buffers. Buffering run and data arraysstored in main memory in DMS memory avoids multiple accesses to the samearray in main memory, thus reducing the overall power consumed by theDMS, and improving performance of decompressing tabular data within theDMS. Likewise, when performing ARLE compression, the DMS creates the runand data arrays in local DMS memory and moves the arrays to main memorywhen the local memory fills. Using the local DMS memory for compressionhas benefits similar to those described for using local DMS memory fordecompression.

The total size of a run and data array depends in part on the number ofrows being moved or copied from the source memory location. The size ofthe arrays also depends in part on the width of the column of tabulardata that is being moved or copied from the source memory location andthe average compression ratio of the column of tabular data. The size ofthe run array depends on the maximum run value that can be stored. Inone embodiment, a run element is one byte wide. For example, if thewidth of the column of tabular data is 2 bytes, the number of rows beingmoved of that column tabular data is 256, and the average compressionratio is 1:4, then the total size of the run array is 256/4 or 64 bytesand the total size of the data array is (256/4)*(width of the column oftabular data) or (256/4)*2, or 128 bytes. When performing decompression,the run and data arrays are moved or copied from a source memorylocation to the local DMS memory unit coupled with the ARLEcompression/decompression block using descriptors.

A core processor configures an auxiliary type descriptor to provide theaddress of the run array to the data movement system. The descriptortype field of the auxiliary descriptor comprises a value that indicatesthat the descriptor is an auxiliary type descriptor. In an embodiment,that value is a sequence of binary numbers that indicate to thedescriptor channel block that the descriptor is an auxiliary typedescriptor. The descriptor channel block decodes the auxiliarydescriptor similarly to the methods described above. The descriptorchannel block determines the control information for the auxiliarydescriptor similarly to the methods described above.

The run address provided in the auxiliary descriptor is the startaddress of the run. In an embodiment, the auxiliary descriptor comprisesa “Run Address” field and the run address is provided as the value ofthe “Run Address” field. In an embodiment, the width of the run array islimited to one byte. The descriptor channel block includes thedescriptor type of the auxiliary descriptor and the run address withinthe control information determined by the descriptor channel block. Thedescriptor channel block transmits the control information of theauxiliary descriptor to a data movement engine similar to the methodsdescribed above.

Since the descriptor is an auxiliary descriptor, the data movementsystem does not move any data from a source memory location to adestination memory location. Instead, the data movement system storesthe values provided in the auxiliary descriptor to use it in processingthe data descriptor that follows the auxiliary descriptor. Thus, thedata movement engine, based on the control information and in particularthe descriptor type, determines that the descriptor is an auxiliarydescriptor and stores the run address provided in the controlinformation in a register and does not generate any read requests to thesystem master bus block interface to retrieve the run array from the runaddress location.

After configuring the auxiliary type descriptor, the very nextdescriptor configured by the core processor is a data descriptor. Theinformation provided in the auxiliary type descriptor preceding the datadescriptor will be used in processing the data descriptor. The datadescriptor provides the starting address of the aligned run lengthencoded tabular data in a source memory unit, such as the main memory oranother memory unit. This is what was referred to as the data array inthe preceding paragraphs. The “Rows” field of this data descriptorcomprises information about the number of rows that will result afterthe aligned run length encoded tabular data is decoded. The “Width”field of the data descriptor comprises a value indicating the columnwidth of the data array available at the starting address of the dataarray, which is provided in the data descriptor.

The data descriptor following the auxiliary descriptor initiates themovement of the run array needed in run length aligned decoding of thetabular data. The data movement engine generates a read request for therun array where the source address included in the read request is theRun address from the auxiliary descriptor that was stored in a registeraccessible by the data movement engine. The data movement enginetransmits the read request to the system bus interface master block. Thedata movement engine also generates a read request for the data arrayand transmits the read request to the system bus interface master block.

The system bus interface master block retrieves the run and data arraysfrom their respective source memory locations similar to the methodsdescribed above. The system bus interface master block transmits thearrays to the data movement engine. The data movement engine decodes thedata array using the run array. The decoded run length aligned encodeddata is stored in the destination memory location specified in the datadescriptor similar to the methods described above. The destinationmemory location in one embodiment can either be in DMEM associated withthe originating descriptor channel block of the data descriptor (such as102 a in FIG. 1) or in DMS memory to be used for subsequent DMSprocessing (150 in FIG. 1).

Data Manipulation Operation Blocks

FIG. 5 illustrates an example arrangement of data manipulation operationengines. For the purposes of illustration, a clear example of datamanipulation operations are shown using elements of FIG. 1. FIG. 5depicts a plurality of data manipulation operation blocks within each ofdata movement engines 130 a, 130 b, 130 c, and 130 d.

FIG. 5 comprises stride operation block 509, scatter operation block510, gather operation block 511 and ARLE decompression block 512. Asdescribed above, system bus interface master block 123 forwards datarequests to the source memory location and also receives data, includingtabular data, from the source memory location. System bus interfacemaster block transmits data received, in response to the read requests,from the source memory location and control information of thedescriptor that requested the data to arbitration unit 516. Arbitrationunit 516 comprises multiplexer 516 a and arbiter 516 b. Multiplexer unit516 a transmits data received from the source memory location andcontrol information of a descriptor to routing unit 514.

Routing unit 514, based on the control information received frommultiplexer 516 a, transmits the data received from the multiplexer 516a to either one of the data manipulation operation blocks 509, 510, 511,512 or to routing unit 502, comprising multiplexer 502 a and routingcontroller 502 b. For example, if control information received frommultiplexer 516 a does not indicate that any data manipulationoperations are to be performed, then the tabular data and the controlinformation received from multiplexer 516 a is transmitted tomultiplexer 502 a. Therefore, the data movement system providesflexibility in skipping one or more data manipulation operation blocksrather than wasting clock cycles or data manipulation operation blockresources when performance of data manipulation operations is notrequired.

Similarly, if control information received from multiplexer 516 aindicates one or more data manipulation operations, then the tabulardata and the control information received from multiplexer 516 a istransmitted to the appropriate data manipulation operation block.Routing unit 514 may be configured with a particular order in which datamanipulation operations are to be performed on a set of tabular datawhen the control information indicates that more than one datamanipulation operation is to be performed on the data received frommultiplexer 516 a.

An example order in which data manipulation operations are to beperformed on a set of tabular data is, first, decompression of thetabular data by an ARLE operation block, if the control informationassociated with that tabular data indicates that such an operation is tobe performed. Then, a gather operation is performed on the decompressedtabular data, if the control information indicates that a gatheroperation should be performed. Following the gather operation, a scatteroperation is performed on the tabular data remaining after the gatheroperation, if the control information indicates that a scatter operationis to be performed. Finally, a stride operation is performed on thetabular data upon which the scatter operation is performed, if thecontrol information indicates that a stride operation should beperformed. This example order of data manipulation operations isillustrated in FIG. 5.

In FIG. 5, routing unit 514 is configured to route tabular data receivedfrom multiplexer 516 a to ARLE decompression block 512 first, if controlinformation received from multiplexer 516 a indicated that the tabulardata should be decompressed. ARLE decompression block 512 transmits thedecompressed tabular data and the associated control information torouting unit 508. Routing unit 508, based on the control information,determines whether additional data manipulation operations are requestedor required and transmits the data accordingly. Suppose the controlinformation indicates that a gather operation should also be performed,then routing unit 508 transmits the tabular data resulting from the ARLEdecompression and the control information to multiplexer 515 c, whichtransmits it to gather operation block 511.

Gather operation block 511 performs the gather operation as describedabove and transmits the resulting tabular data and the controlinformation to routing unit 507. Routing unit 507 determines if thecontrol information indicates performance of any other data manipulationoperations on the tabular data. In an embodiment, routing unit 507 onlychecks for whether the control information indicates that either ascatter or a stride operation is to be performed, since the nextoperations in the order are a scatter operation and/or a strideoperation, but not an ARLE operation. Additionally, routing unit 507 cantransmit to either the scatter operation block 510 or the strideoperation block 509, but cannot transmit to ARLE decompression block512.

Suppose that the control information indicated that a stride operationis to be performed, then routing unit 507 transmits the resultingtabular data and the control information to multiplexer 515 a.Multiplexer 515 a transmits the tabular data and the control informationto stride operation block 509. Thus, scatter operation block 510 iscompletely skipped over, saving the resources of scatter operation block510. Stride operation block 509 transmits the resulting tabular data torouting unit 505. Routing unit 505, based on the destination memorylocation indicated in the control information, transmits the resultingtabular data and the control information to either multiplexer 501 a, ormultiplexer 502 a. Similarly, routing units 506, 507, 508, based on thedestination memory location, may transmit data from their respectivedata manipulation operation blocks to multiplexer 501 a or multiplexer502 a, if the control information indicated that no other datamanipulation operation is requested or required.

Data transmitted for multiplexer 501 a is destined for DMS memory. Thedata is initially aligned and accumulated in data alignment/accumulator503, which writes the data to the destination memory location within DMSmemory. Arbiter 501 b is an arbiter for multiplexer 501 a.

Data transmitted for multiplexer 502 a is destined for DMEM. The data isaligned and accumulated in data alignment/accumulator 504, which writesthe data to the destination memory location within DMEM memory. Arbiter502 b is an arbiter for multiplexer 502 a.

Therefore, the output of each of the data manipulation operation blocksdescribed above may be cascaded into an input of one of the other datamanipulation operation blocks. For example, the output from the gatheroperation block can be fed in as the input into the scatter operationblock. Similarly the output from ARLE compression/decompression blockcan be fed into the input of a gather, scatter, or a stride operationblock. Furthermore, a data movement engine may skip some or all of thedata manipulation operation blocks based on the control informationprovided by the descriptors.

Finally, the data manipulation operation blocks may each be concurrentlyexecuting (i.e. in the same clock cycles) on data manipulationoperations on tabular data for different descriptors. For example,routing unit 514 routes tabular data received from multiplexer 516 a fora first descriptor to ARLE decompression block 512. ARLE decompressionblock 512 decompresses the tabular data and transmits the decompressedtabular data and the associated control information for the descriptorto routing unit 508. Routing unit 508 transmits the tabular dataresulting from the ARLE decompression and the control information forthe first descriptor to multiplexer 515 c.

Multiplexer 515 c transmits the tabular data to gather operation block511. Meanwhile, routing unit 514 routes tabular data received frommultiplexer 516 a for a second descriptor to ARLE decompression block512. ARLE decompression block 512 decompresses the tabular data for thesecond descriptor while (i.e. within the same clock cycles) gatheroperation block 511 performs a gather operation on the tabular data forthe first descriptor.

Method of Moving Data and Performing Data Manipulation Operationswithout Executing Software Programs

FIG. 6 illustrates an example process for moving data using hardwarecircuitry without execution of software. In an embodiment, theoperations described for FIG. 6 may be performed by the data movementsystem described in FIG. 1.

In steps 601 a and 601 b, in response to a particular memory locationbeing pushed into a first register within a first register space that isaccessible by a first set of electronic circuits, said first set ofelectronic circuits accesses a descriptor stored at the particularmemory location. In an embodiment, the particular memory location may bea memory address within a DMEM local to a core processor that programmedthe descriptor. In an embodiment the first set of electronic circuitsmay be the group of electronic circuits of any DMAD described in FIG. 1.

In step 602, the first set of electronic circuits determine, based onthe descriptor, control information indicating said one or more datamanipulation operations to perform on the tabular data. In anembodiment, the descriptor may specify a source memory location and adestination memory location for said tabular data. In some embodiments,the source memory location may be within a main memory such as a DDR andthe destination memory location may be within a DMEM as described inFIG. 1. In some embodiments, the source memory location may be within aDMEM and the destination memory location may be within a main memory. Inan embodiment, the descriptor may specify a width of a column of tabulardata, a number of rows of tabular data, and one or more datamanipulation operations to perform on the column of data.

In step 603, the first set of electronic circuits transmit, using ahardware data channel, the control information to a second set ofelectronic circuits to perform the one or more data manipulationoperations. In an embodiment, the second set of electronic circuits maybe the group of electronic circuits within the DMAC described in FIG. 1.In an embodiment, a single DMAC, as described in FIG. 1, may processinstructions from a plurality of DMAD units described in FIG. 1.Therefore, because a single DMAC services a plurality of DMAD units, thedata movement system described herein significantly reduces gate count,area and power necessary to move data.

In step 604 a, according to the control information, said second set ofelectronic circuits retrieve said tabular data from a source memorylocation. In an embodiment, the source memory location may be specifiedby the descriptor. In step 604 b, the second set of electronic circuitsapply one or more data manipulation operations to said tabular data togenerate a data manipulation result. In an embodiment, the datamanipulation operations are performed prior to storing the tabular datain the destination memory location at a sustained high bandwidth into aformat expected by the core processor. In step 604 c, the second set ofelectronic circuits cause said data manipulation result to be stored ata destination location. In an embodiment, the destination location maybe specified by said descriptor.

Extensions and Alternatives

In the foregoing specification, embodiments of the invention have beendescribed with reference to numerous specific details that may vary fromimplementation to implementation. Thus, the sole and exclusive indicatorof what is the invention, and is intended by the applicants to be theinvention, is the set of claims that issue from this application, in thespecific form in which such claims issue, including any subsequentcorrection. Any definitions expressly set forth herein for termscontained in such claims shall govern the meaning of such terms as usedin the claims. Hence, no limitation, element, property, feature,advantage or attribute that is not expressly recited in a claim shouldlimit the scope of such claim in any way. The specification and drawingsare, accordingly, to be regarded in an illustrative rather than arestrictive sense.

What is claimed is:
 1. A method for moving tabular data to on-chipmemory: in response to a particular memory location being pushed into afirst register within a first register space that is accessible by afirst set of electronic circuits: said first set of electronic circuitsaccessing a descriptor stored at the particular memory location, whereinthe descriptor indicates: a width of a column of tabular data, a numberof rows of said column of tabular data, and one or more tabular datamanipulation operations to perform on said column of tabular data; asource memory location for said column of tabular data a destinationmemory location for a data manipulation result of said one or moretabular data manipulation operations; and the first set of electroniccircuits determining, based on the descriptor, control informationindicating said one or more tabular data manipulation operations toperform on said column of tabular data; the first set of electroniccircuits transmitting, using a hardware data channel, the controlinformation to a second set of electronic circuits to perform the one ormore tabular data manipulation operations; according to the controlinformation, said second set of electronic circuits retrieving saidcolumn of tabular data from said source memory location; applying saidone or more tabular data manipulation operations to said column oftabular data to generate said data manipulation result; and causing saiddata manipulation result to be stored at said destination memorylocation.
 2. The method of claim 1, wherein the descriptor indicates atype of the descriptor.
 3. The method of claim 1, wherein the descriptorindicates a wait condition that should be satisfied prior to the step ofthe first set of electronic circuits determining the controlinformation.
 4. The method of claim 1, further comprising: the first setof electronic circuits adding the descriptor to a hardware managedlinked list; wherein adding the descriptor to a hardware managed linkedlist comprises writing the particular memory location to a particulardescriptor field of a second descriptor.
 5. The method of claim 1,wherein the descriptor indicates automatically incrementing said sourcememory location and a source counter.
 6. The method of claim 5, furthercomprising: in response to a second memory location being pushed intothe first register: said first set of electronic circuits accessing asecond descriptor stored at the second memory location, wherein thesecond descriptor indicates: the source memory location for said columnof tabular data; said second set of electronic circuits determining anew source memory location based at least in part on a value of thesource counter.
 7. The method of claim 6, further comprising: said firstset of electronic circuits incrementing a source counter value by oneafter the step of the first set of electronic circuits transmitting thecontrol information to the second set of electronic circuits.
 8. Themethod of claim 1, further comprising: in response to a second memorylocation being pushed into the first register: said first set ofelectronic circuits accessing a second descriptor stored at the secondmemory location, wherein the second descriptor indicates: the particularmemory location.
 9. The method of claim 8, further comprising: whereinthe second descriptor indicates an iteration count; the first set ofelectronic circuits determining that the iteration count is not zeroprior to accessing the descriptor stored at the particular memorylocation.
 10. The method of claim 1, wherein the descriptor indicates anotification flag.
 11. A method comprising: a data processing corecoupled with a first on-chip memory pushing a particular memory addressof a descriptor into a first register within a first register space thatis accessible by a first set of electronic circuits that is coupled tosaid first on-chip memory; wherein the descriptor indicates a width of acolumn of tabular data, a number of rows of said column of tabular data,and a data manipulation operation to perform on said column of tabulardata; in response to said particular memory address of said descriptorbeing pushed into said first register by said data processing core: thefirst set of electronic circuits, using the particular memory address inthe first register, accessing the descriptor in the first on-chipmemory; the first set of electronic circuits determining, based on thedescriptor, control information indicating one or more data manipulationoperations to perform; in response to determining the controlinformation: the first set of electronic circuits transmitting, using ahardware data channel, the control information to a second set ofelectronic circuits to perform said one or more data manipulationoperations.
 12. The method of claim 11, further comprising: the dataprocessing core determining that said particular memory address isavailable in a second register within a second register space that isdesignated to store memory addresses of the first on-chip memory thatare free; and in response to the particular memory address beingavailable in the second register, the data processing core storing thedescriptor at the particular memory address.
 13. The method of claim 11,further comprising: wherein the data processing core determines whethera flag, indicating that one or more memory addresses of the firston-chip memory is available in registers within a second register space,is set, wherein the second register space is designated to store memoryaddresses of the first on-chip memory that are free; in response to theflag being set: the data processing core determining that the particularmemory address is available in a particular register within the secondregister space.
 14. The method of claim 11, further comprising: thefirst set of electronic circuits adding the descriptor to a linked listmanaged by hardware of a data movement system.
 15. The method of claim14, wherein adding the descriptor to the linked list is performed byspecifying in a link address field of the descriptor a memory address ofa second descriptor that is different from the descriptor, wherein thesecond descriptor is in a second register within the first registerspace.
 16. The method of claim 11, wherein the descriptor is a datadescriptor that specifies movement of data from one memory to anothermemory.
 17. The method of claim 16, wherein the descriptor indicates adirection in which the movement of data from one memory to anothermemory occurs.
 18. The method of claim 11, wherein the descriptor is acontrol descriptor that at least specifies configuration informationcorresponding to one or more registers of the data movement system. 19.The method of claim 11, wherein the descriptor is an auxiliarydescriptor that specifies information which assists in processing ofanother descriptor.
 20. The method of claim 11, wherein the dataprocessing core is the only data processing core that can access thefirst on-chip memory within a data movement system comprising multipledata processing cores.